Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use get_branch in get_behind_by instead of get_branches #79

Merged
merged 3 commits into from
Aug 30, 2023
Merged

Use get_branch in get_behind_by instead of get_branches #79

merged 3 commits into from
Aug 30, 2023

Commits on Aug 30, 2023

  1. Use get_branch in get_behind_by instead of get_branches 

    This commit changes get_behind_by to use get_branch instead
of get_branches because of a GH API rate limiting issue.

Instead of listing all branches in a repo via the API we now
fetch only the one we are looking for, in this case the base
branch of an open PR.

This commit also makes changes to the requirements by updating
shared to the latest version in order to use get_branch.

Changes had to be made to existing integration tests as they
we re-run, cassettes were updated.

Signed-off-by: joseph-sentry <[email protected]>
    @joseph-sentry
    joseph-sentry committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    e14b962 View commit details
    Browse the repository at this point in the history

  2. run linter 

    Signed-off-by: joseph-sentry <[email protected]>
    @joseph-sentry
    joseph-sentry committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    31b156f View commit details
    Browse the repository at this point in the history

  3. update shared sha 

    Signed-off-by: joseph-sentry <[email protected]>
    @joseph-sentry
    joseph-sentry committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    3de08dc View commit details
    Browse the repository at this point in the history