You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So my client is using a custom preset because we do not use default conventional commit but a custom version where the Jira ticket number gets put in front. I have created this project here which basically wraps the default preset and updates the expected pattern. For a while was working completely fine. From what I can tell the preset that is being given to the changelog generator is always the default preset and the key "name" in my project.json is being ignored. I just "hacked" together this commit here as a proof of concept that works (as we would like it to). Is there a reason why the mentioned preset name in our config is being ignored for the changelog or is this a bug?
Assuming it is a bug then I would be happy to polish that commit a bit so that it can be merged.
The text was updated successfully, but these errors were encountered:
So my client is using a custom preset because we do not use default conventional commit but a custom version where the Jira ticket number gets put in front. I have created this project here which basically wraps the default preset and updates the expected pattern. For a while was working completely fine. From what I can tell the preset that is being given to the changelog generator is always the default preset and the key "name" in my
project.json
is being ignored. I just "hacked" together this commit here as a proof of concept that works (as we would like it to). Is there a reason why the mentioned preset name in our config is being ignored for the changelog or is this a bug?Assuming it is a bug then I would be happy to polish that commit a bit so that it can be merged.
The text was updated successfully, but these errors were encountered: