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

fix(release-notes): Drop the re-classification of commits to "other" in some cases #463

Merged
merged 2 commits into from
Jun 7, 2024

Conversation

sasa-tomic
Copy link
Member

@sasa-tomic sasa-tomic commented Jun 6, 2024

This re-classification was triggering wrongly in some cases, marking feature commits as "other" just because the feature commit was touching many teams.

This is not needed anymore since conventional commits are getting enforced in the IC repo.

@sasa-tomic sasa-tomic requested a review from a team as a code owner June 6, 2024 17:05
@sasa-tomic sasa-tomic changed the title fix(release-notes): Only mark a commit as "other" if >=5 teams are to… fix(release-notes): Move commit to "other" category if >=5 teams own it Jun 6, 2024
@sasa-tomic sasa-tomic changed the title fix(release-notes): Move commit to "other" category if >=5 teams own it fix(release-notes): Drop the re-classification of commits to "other" in some cases Jun 6, 2024
@sasa-tomic sasa-tomic merged commit 075bde7 into main Jun 7, 2024
4 checks passed
@sasa-tomic sasa-tomic deleted the sat-release-notes-team-other-threshold branch June 7, 2024 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants