Reorder release notes labels #2599
Merged
Conversation
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
Problem: Many of our test changes also include markdown file changes, and the docs label is prioritized in our release notes over tests. This means that the docs sections of the notes often contained many tests changes. Solution: Prioritize the test label first over docs to hopefully better organize release notes.
|
@lucacome I'm assuming this is how the labeler works, but do you know if I'm wrong about this? |
|
That's how it works AFAIK |
lucacome
approved these changes
Sep 24, 2024
kate-osborn
approved these changes
Sep 25, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2599 +/- ##
=======================================
Coverage 89.20% 89.20%
=======================================
Files 100 100
Lines 7642 7642
Branches 50 50
=======================================
Hits 6817 6817
Misses 768 768
Partials 57 57 ☔ View full report in Codecov by Sentry. |
bjee19
approved these changes
Sep 25, 2024
salonichf5
pushed a commit
that referenced
this pull request
Oct 8, 2024
Problem: Many of our test changes also include markdown file changes, and the docs label is prioritized in our release notes over tests. This means that the docs sections of the notes often contained many tests changes. Solution: Prioritize the test label first over docs to hopefully better organize release notes.
miledxz
added a commit
to miledxz/nginx-gateway-fabric
that referenced
this pull request
Jan 14, 2025
Problem: Many of our test changes also include markdown file changes, and the docs label is prioritized in our release notes over tests. This means that the docs sections of the notes often contained many tests changes. Solution: Prioritize the test label first over docs to hopefully better organize release notes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Problem: Many of our test changes also include markdown file changes, and the docs label is prioritized in our release notes over tests. This means that the docs sections of the notes often contained many tests changes.
Solution: Prioritize the test label first over docs to hopefully better organize release notes.