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

Feature request #602

Open
Gert-Jan2AT opened this issue Feb 27, 2024 · 1 comment
Open

Feature request #602

Gert-Jan2AT opened this issue Feb 27, 2024 · 1 comment

Comments

@Gert-Jan2AT
Copy link

I'd like the option to be able to ignore strings that match a pattern that nog prevent the commit analyzer from working with DevOps commits.

As is wel documented in this issue (https://developercommunity.microsoft.com/t/Change-default-title-for-pull-request-co/365716), DevOps insists on prefixing a pull request with the text Merged PR ####. This means that the title feat: Updated Program.cs becomes Merged PR 8324: feat: Updated Program.cs af the merge.

If it would be possible te specify een regular expression to ignore these words the problem would be solved. Of course it would be nice to also have the text feat: Updated Program.cs in the release note instead of Merged PR 8324: feat: Updated Program.cs

@travi
Copy link
Member

travi commented Mar 29, 2024

i understand that this is a real problem, but i dont think solving this with a generic regex approach is a solution we are interested in accepting. solutions like this are so generic that they open the door for many additional use cases, which is complexity that we are hesitant to accept permanent support implications for.

in addition, i'm not sure that semantic-release is even the best place to solve something like this anyway. this is an issue with how the commit conventions are handled, so it seems like this would be a more appropriate request for the underlying conventional-changelog project that semantic-release uses. i recommend opening an issue there if this is something that you want to pursue

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

No branches or pull requests

2 participants