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
Unless I'm mistaken it seems message is the only variable available for templating commit entries. I was hoping to put together a changelog with a format something like:
[{{sha}}]({{url}}) {{message}} - {{author.name}}
I was wondering if there's a specific reason why commitMessages() just pulls out the commit message rather retaining the commit object (or a subset of it), which can then pass through the system eventually allowing generateCommitsBody() to template on more than just the commit message? If not, is this something that could be added?
The text was updated successfully, but these errors were encountered:
I was thinking the whole object personally. The size of the full commit object shouldn't cause any issues so I can't think of any reason to limit it to a subset of the properties..
I haven't written any code for it yet. I've only just started poking around the code today so not sure what the scope/complexity of the change would be at the moment.
Unless I'm mistaken it seems message is the only variable available for templating commit entries. I was hoping to put together a changelog with a format something like:
[{{sha}}]({{url}}) {{message}} - {{author.name}}
I was wondering if there's a specific reason why
commitMessages()
just pulls out the commit message rather retaining the commit object (or a subset of it), which can then pass through the system eventually allowinggenerateCommitsBody()
to template on more than just the commit message? If not, is this something that could be added?The text was updated successfully, but these errors were encountered: