Skip to content

What's the best way to handle asynchronous GitHub API calls? #9

Open
@LearningNerd

Description

@LearningNerd

Some GitHub API calls trigger actions that take a while to complete, so the response from GitHub might not have the information required. (For example, there's a delay between forking a repo and when that repo is actually available for additional actions.)

I noticed a while ago that Mavo.io addressed that issue, so I should take a closer look at the source code for some ideas. I wonder if there are other examples or tutorials on this, or if GitHub offers any suggestions in their documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions