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

Add semanticCommitType awareness to generateBranchConfig() #31979

Open
rarkins opened this issue Oct 16, 2024 · 0 comments · May be fixed by #32069
Open

Add semanticCommitType awareness to generateBranchConfig() #31979

rarkins opened this issue Oct 16, 2024 · 0 comments · May be fixed by #32069
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Oct 16, 2024

Describe the proposed change(s).

Renovate is not aware of the meaning of values of semanticCommitType - they're all just strings. Currently, when a branch has mixed values for semanticCommitType then whichever is the first update in the branch is used as the value for branch semanticCommitType.

Instead, we could:

  • Add awareness of the "importance" of semanticCommitType values (e.g. fix is more important than chore)
  • Implement this awareness in
    export function generateBranchConfig(
    so that the "most important" semanticCommitType value is chosen from the branch, instead of the first.
@rarkins rarkins added type:feature Feature (new functionality) priority-4-low Low priority, unlikely to be done unless it becomes important to more people labels Oct 16, 2024
@breadadams breadadams linked a pull request Oct 22, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant