Comments (8)
I was hoping to have the same behaviour here, if we generate pre-releases constantly, and after some time we generate a release, the release note is empty, it would make sense to have an option to consolidate all the pre-releases changes in the release.
I believe the rule shoul be:
pre-release
- Consolidate all changes since the lastpre-release
orrelease
release
- Consolidate all changes since the lastrelease
from python-semantic-release.
An interesting concept, this might be a place for a jinja macro to preprocess the release history object that is passed to the environment of the template renderer and then loop through the resulting object.
I've personally never written a jinja macro but that would be where I would start.
from python-semantic-release.
After re-reading this, I'm not sure what is your intended outcome for the changelog?
- Consolidate all prereleases commits to be under the full release version without the prerelease tags as sections?
Or
- Consolidate all prereleases commits under the full release version while maintaining each prerelease section?
from python-semantic-release.
What would be interesting is that each "pre-release" has its own change log (as currently).
And when i create the "release", all the previous commits of the different RCs appear in the github changelog.
=> https://github.com/{org}/{repo}/releases/tag/vX.X.X
Actually, just last commit beetwen last RC and release is appear.
from python-semantic-release.
I think we are talking past each other given the terminology. I was specifically talking about the generation of CHANGELOG.md
but it seems you were more interested in the GitHub Release Notes (a per version section of the changes).
My understanding is that right now, the release notes are properly generated for each pre-release but you would like to have the newest full tag release to include all of the commits between it and the last full release as if the prereleases never existed. Is this correct?
Actually, just last commit beetwen last RC and release is appear.
In other words: At the current moment, only commits between the last prerelease and the new release are posted in the new versions release notes. This is my understanding, yes.
I do not believe this is possible at the current time. I have recently made a fix (#822) which likely will provide this functionality for repos that follow the Git Flow merging strategy. I have not yet tested other strategies and I do not know their outcomes but might be related to making this possible.
from python-semantic-release.
@ibiscp, thank you for providing your input
from python-semantic-release.
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?
from python-semantic-release.
Still in the backlog but a valuable improvement nonetheless
from python-semantic-release.
Related Issues (20)
- Allow --no-tag to overwrite --commit HOT 2
- Running github actions after python-semantic-release? HOT 3
- Default changelog template options HOT 6
- Ability to easily autolink to PRs in changelogs HOT 3
- Inconsistent carriage returns in generated changelogs HOT 1
- Add support for adding .cff-file variable in version_variables HOT 2
- Change log should contain only messages that change user experience HOT 5
- Feature request: Support git push options HOT 2
- Allow `version --print` outside of release branches
- Ability to add labels/comments to linked issues/PRs HOT 1
- Support CI_JOB_TOKEN now that Gitlab added the option for it to push to its own repository which will be released in 17.2 (July 18th) HOT 1
- Changelog file destination must be inside of the repository directory. HOT 5
- How to generate a CHANGELOG like version 7 and below? HOT 7
- When template folder is present, changelog_file is ignored HOT 4
- jinja2.exceptions.UndefinedError: 'context' is undefined HOT 10
- Changelog Testing fails when run across midnight HOT 1
- Adding allowed_tags not working - Angular or Scipy parser HOT 5
- Github Actions - Include submodules in assets HOT 3
- Getting "Template directory must be inside of the repository directory." error when not specifying template_dir option. HOT 5
- KeyError: 'changelog' when running in GitHub actions HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from python-semantic-release.