chore(ci): improve message when do-not-merge label is present#7505
Merged
leandrodamascena merged 2 commits intoaws-powertools:developfrom Oct 10, 2025
Merged
Conversation
pull-request-size
bot
added
the
size/XS
boring-cyborg
bot
added
the
github-actions
tonnico
changed the title
sthulb
approved these changes
Oct 10, 2025
Contributor
|
@tonnico Mind creating an issue for this? |
leandrodamascena
changed the title
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issue number: closes #7507
Summary
Improve failing message for minimum requirements.
Changes
User experience
It took me a while to find out, why "minimum requirements" check is failing. So I add the filter reason to the message.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.