-
Notifications
You must be signed in to change notification settings - Fork 202
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
check if PR is already merged in --merge-pr #3502
check if PR is already merged in --merge-pr #3502
Conversation
hm, I suppose this will break tests that use merged PRs... |
@migueldiascosta Is this still WIP? |
No, forgot to re-edit the title |
easybuild/tools/github.py
Outdated
@@ -1331,6 +1331,9 @@ def merge_pr(pr): | |||
force = build_option('force') | |||
dry_run = build_option('dry_run') or build_option('extended_dry_run') | |||
|
|||
if pr_data['merged'] and not dry_run: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also take into account closed PRs?
Also, why doesn't this make the merge_pr
test in test/framework/options.py
fail?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also take into account closed PRs?
will do
Also, why doesn't this make the
merge_pr
test intest/framework/options.py
fail?
that's why I added the and not dry_run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we update the test so it tries --merge-pr
without dry run on a merged/closed PR to cover this change in the tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
fixes #3501