-
Notifications
You must be signed in to change notification settings - Fork 381
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
Add an option to disable changelog generation #2007
Comments
I'm using release-please with a monorepo and I prefer one changelog for the entire project, and not for the subprojects. |
An option to disable changelog generation is feasible, but not something we're planning on implementing. We would welcome a pull request to potentially add the feature. |
@chingor13, I'd love to help you ship it. Just, let me know what kind of API you find best to disable changelog generation. I proposed If we can agree on the API here, I will try to pen a pull request this/next week. Thanks! |
Thanks! I think we want this as a manifest config option (schema: https://github.com/googleapis/release-please/blob/main/schemas/config.json). The CLI option is an optional inline interface into specifying a manifest config (but we prefer folks configure a manifest config). As for the naming of the option, I would suggest |
+1 on the manifest option. It would be nice to be able to skip-change logs on packages in a repo but still keep the overall changelog. I think the manifest would allow this granularity. |
@kettanaito do you have a branch for this work yet ? 👀 need a hand ? |
@unjust I see that you already have some WIP ... did you open a PR for it? (or willing to continue working on it?) |
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
I'm frustrated that Release Please always generates and commits a
CHANGELOG.md
file. It is the developer's decision to keep that file or not, and it must not be enforced by this tool. For instance, I find changelog files to be redundant and provide little use to the end consumers of my software. I use GitHub releases as the changelog, which Release Please already fills in using the same content as the changelog.Describe the solution you'd like
A
--disable-changelog
boolean flag which, when set totrue
, skips the changelog generation phase altogether.Describe alternatives you've considered
changelog-types: ""
, gets ignored by the tool.changelog-path
to the path ignored in Git. No effect either.The text was updated successfully, but these errors were encountered: