Skip to content

Conversation

@ViacheslavKudinov
Copy link
Contributor

@ViacheslavKudinov ViacheslavKudinov commented Nov 11, 2025

Resolves #2865


Before the change?

  • 🤷‍♂️ it could be the situation when one PR will get more than one label as the changes can be based on branch name and changed files on specific paths covered by config.
    It may result that the same PR will come under more than one release category.

After the change?

  • ✅ lets keep only branch name based labeling for some time and then decide if we would like to extend to path-based labeling again

Pull request checklist

  • Schema migrations have been created if needed (example)
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@ViacheslavKudinov ViacheslavKudinov changed the title chore: clean up labeler configuration by removing changed-files based labeling chore(labeler): clean up labeler configuration by removing changed-files based labeling Nov 11, 2025
@ViacheslavKudinov ViacheslavKudinov marked this pull request as ready for review November 11, 2025 18:17
@ViacheslavKudinov ViacheslavKudinov changed the title chore(labeler): clean up labeler configuration by removing changed-files based labeling chore(labeler): adjust labelerer configuration by commenting changed-files based approach Nov 11, 2025
@ViacheslavKudinov ViacheslavKudinov changed the title chore(labeler): adjust labelerer configuration by commenting changed-files based approach chore(labeler): adjust labelerer configuration by commenting changed-files based approach to keep only branch name based one Nov 12, 2025
@ViacheslavKudinov ViacheslavKudinov changed the title chore(labeler): adjust labelerer configuration by commenting changed-files based approach to keep only branch name based one chore(labeler): OPTIONALLY to adjust labelerer configuration by commenting changed-files based approach to keep only branch name based one Nov 12, 2025
@ViacheslavKudinov ViacheslavKudinov changed the title chore(labeler): OPTIONALLY to adjust labelerer configuration by commenting changed-files based approach to keep only branch name based one chore(labeler): OPTIONALY to adjust labelerer configuration by commenting changed-files based approach to keep only branch name based one Nov 12, 2025
@nickfloyd nickfloyd moved this from Backlog to In Progress in Terraform Provider Nov 20, 2025
@nickfloyd nickfloyd moved this from In Progress to On Deck in Terraform Provider Nov 20, 2025
@nickfloyd nickfloyd added this to the v7 Next milestone Nov 20, 2025
@nickfloyd nickfloyd moved this from On Deck to In Progress in Terraform Provider Nov 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

[MAINT]: Improve efficiency for generating release notes

2 participants