Add extra details to release from commit message #223
Comments
|
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
|
Interesting idea, need to put more thought into how this can be added. I'm leaning towards a paragraph section in a commit message but unfortunately that is not standard to commit parsers. One such answer could be a cli option or interactive cli prompt but this would be problematic for all the different types of automation this project supports and recommends. I partially think that the deprecation message goes into the breaking changes section of the commit which will be extracted separately during parsing. It would take a custom changelog to document them in a separate section. Either way, still in the backlog and open to community PRs. |
|
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
|
Still in the backlog |
|
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
|
Considering using a the keyword heading of Then in the changelog it will go after any BREAKING CHANGE paragraphs and be place under the title |
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…rkdown template Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…rkdown template Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…rkdown template Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…rkdown template Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…rkdown template Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…rkdown template Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
…ed statements in commits Resolves: python-semantic-release#223
… statements in commits Resolves: python-semantic-release#223
…rkdown template Resolves: python-semantic-release#223
…eStructuredText template Resolves: python-semantic-release#223
🎉 This issue has been resolved in Version 9.18.0 🎉You can find more information about this release on the GitHub Releases page. |
Description
Allow some way of adding extra details into the changelog, similar to the text I added manually to v6.1.0. This would be done via the commit message.
Use cases
Possible implementation
Something similar to
BREAKING CHANGE:at the beginning of a paragraph.The text was updated successfully, but these errors were encountered: