Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to labeler 5.0.0 #211

Merged
merged 4 commits into from
Jan 31, 2024
Merged

Upgrade to labeler 5.0.0 #211

merged 4 commits into from
Jan 31, 2024

Conversation

llucax
Copy link
Contributor

@llucax llucax commented Jan 2, 2024

This also fix the matching rules, that were broken, probably because the version before 5.0.0 didn't support the flexible glob matching or it was misused.

Fixes #194.

@llucax llucax requested a review from a team as a code owner January 2, 2024 10:36
@llucax llucax added this to the v0.9.0 milestone Jan 2, 2024
@llucax llucax self-assigned this Jan 2, 2024
@llucax llucax force-pushed the labeler-5 branch 2 times, most recently from 8022eec to f12b7e4 Compare January 2, 2024 13:02
@llucax llucax enabled auto-merge January 2, 2024 13:50
@github-actions github-actions bot added the part:tests Affects the unit, integration and performance (benchmarks) tests label Jan 3, 2024
@llucax llucax added type:bug Something isn't working type:enhancement New feature or enhancement visitble to users part:cookiecutter Affects the generation of projects using cookiecutter part:ci Affects the GitHub workflow and other parts for running CI labels Jan 3, 2024
@llucax llucax removed this from the v0.9.0 milestone Jan 3, 2024
@github-actions github-actions bot removed part:cookiecutter Affects the generation of projects using cookiecutter part:ci Affects the GitHub workflow and other parts for running CI labels Jan 3, 2024
This also fix the matching rules, that were broken, probably because the
version before 5.0.0 didn't support the flexible glob matching or it was
misused.

Signed-off-by: Leandro Lucarella <[email protected]>
RELEASE_NOTES.md Outdated
@@ -24,6 +24,36 @@ To upgrade without regenerating the project, you can follow these steps:

Go to the repository settings -> **Rules** -> **Rulesets** -> **Protect version branches** -> **Bypass list** -> **Add bypass** -> Select **Maintain** role and change the dropdown bypass rule to use **Pull requests** instead of **Always**.

- The `labeler` action was upgraded to 5.0.0. This needs a new configuration file.

If you didn't diverged much from the default configuration (and you are not using exclusion rules), you can update the configution file by running this script in the root of your repository:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*didn't diverge or haven't diverged

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

configution => configuration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to fix both typos. Thanks!

Signed-off-by: Leandro Lucarella <[email protected]>
@llucax llucax added this pull request to the merge queue Jan 31, 2024
Merged via the queue into frequenz-floss:v0.x.x with commit c293cdd Jan 31, 2024
14 checks passed
@llucax llucax deleted the labeler-5 branch January 31, 2024 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:tests Affects the unit, integration and performance (benchmarks) tests type:bug Something isn't working type:enhancement New feature or enhancement visitble to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ci: Update the pull request labeler action to v5
2 participants