fix: always create backport check run #253
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.
Fixes #251.
There's currently several cases where the backport check run for a target branch can be out-of-sync (or missing altogether) with trop's backport attempts. This PR aims to ensure there's always a check run when trop is executing a backport, and that it's always updated with the outcome of that backport execution attempt. This should ensure that a failure to backport after the PR is merged won't have a conflicting state where the check run (done when the PR was labeled) is clean.