fix release-plan unlabelled changes PR #1871
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
release-plan is supposed to report unlabelled PRs in the Prepare Release pr but it hasn't been working correctly. I figured out that the issue is that the pull request action won't open a PR unless there are some file changes and `stderr.log` is covered by our .gitignore file. This PR fixes that and it also makes sure that the stderr.txt doesn't make it into the PR when the release-plan job is successful.
NullVoxPopuli
approved these changes
Apr 10, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
release-plan is supposed to report unlabelled PRs in the Prepare Release pr but it hasn't been working correctly. I figured out that the issue is that the pull request action won't open a PR unless there are some file changes and
stderr.logis covered by our .gitignore file.This PR fixes that and it also makes sure that the stderr.txt doesn't make it into the PR when the release-plan job is successful.