HDDS-6324. Do not trigger CI by reopening PR #3092
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
CI can be retriggered for PRs in three ways:
New (empty) commit makes CI history visible in the PR, but it triggers two runs: one for the PR and another in the source branch.
Github has recently improved run result view by including UI element for previous runs. Earlier this was available only via the repository's Actions view, which lists all action runs, so finding the specific run was not easy.
Closing/reopening to trigger build has two disadvanteges: it produces unnecessary noise (in the PR and email notifications), and CI history is still hard to find.
We should disable build on reopen and prefer "re-run all checks".
https://issues.apache.org/jira/browse/HDDS-6324
How was this patch tested?
Not tested, trivial change.
Workflow file is validated by CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/1846707702