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.

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

Verify that the pull request head commit exists #55

Merged
merged 1 commit into from Mar 13, 2019

Conversation

bluekeyes
Copy link
Member

Some GitHub APIs have a delay propagating information about new commits, particularly when the commits come from forks. While I believe the APIs we currently use are safe, if they are not, the policy should fail closed with an error instead of potentially failing open, as it does currently.

Also reorganize some test data so that it is more consistent, making it easier for tests to pass this new check.

Fixes #47.

Some GitHub APIs have a delay propagating information about new commits,
particularly when the commits come from forks. While I believe the APIs
we currently use are safe, if they are not, the policy should fail
closed with an error instead of potentially failing open, as it does
currently.

Also reorganize some test data so that it is more consistent, making it
easier for tests to pass this new check.
@bluekeyes bluekeyes changed the base branch from bkeyes/remove-timeline-api to develop March 13, 2019 17:17
@bluekeyes bluekeyes merged commit 856c746 into develop Mar 13, 2019
@bluekeyes bluekeyes deleted the bkeyes/check-head-commit branch March 13, 2019 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

invalidate_on_push fails open if GitHub APIs are delayed
2 participants