Skip to content

Make GitHub sponsors script a little more robust #62

@BenJam

Description

@BenJam

So I just ran the GitHub sponsors script for the firs title in... a while but it took nearly 2 hours of hand holding to process the ~275 individual contributions that were in the latest payouts.

Generally I think it would be great if the script was able to back off and retry, or log a failure and continue processing a list. Some common failures below:

  • Client network socket disconnected before secure TLS connection was established: happened 4-5 times randomly, I dont think this was my side but it could be.
  • collective not found : yes, I know I should have picked this up in a dry run but, just in case...
  • Adding funds is not allowed for frozen accounts: not something that's picked up in the dry run.

In addition the collective not found error was thrown when attempting to add for a project rather a Collective. I think it should be able to support project given slugs are all unique.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions