Always include next steps in GitHub message #1308
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 #1307
Before this change, the next steps instructions (which include label changes and bors directives) were only showed if the results were relevant. However, we should always show next steps even if the results aren't relevant.
This has a few interesting changes to current behavior:
S-waiting-on-perf
label will be removed when the try run finishes@bors rollup=never
perf-regression
label will be removed if the run returns no relevant perf resultsAll these changes are how things worked in the past, and I believe are the right behavior.