Skip to content
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

Enhancing releases with diff tag PRs #622

Open
axsaucedo opened this issue Nov 17, 2024 · 3 comments
Open

Enhancing releases with diff tag PRs #622

axsaucedo opened this issue Nov 17, 2024 · 3 comments

Comments

@axsaucedo
Copy link
Collaborator

Currently the github script publishes releases once a month which allows watchers to be notified.

As an added feature we should include the PRs and commits included in the release; now that we have explicit PR namings, we should be able to easily generate a comprehensive summary.

We can explore which tool would be the simplest to achieve this, such as the github-changelog-generator, etc

@zhimin-z
Copy link
Collaborator

zhimin-z commented Nov 26, 2024

Currently the github script publishes releases once a month which allows watchers to be notified.

As an added feature we should include the PRs and commits included in the release; now that we have explicit PR namings, we should be able to easily generate a comprehensive summary.

We can explore which tool would be the simplest to achieve this, such as the github-changelog-generator, etc

For each release, the PR/commit history messages would be shown in the release page, why would we explicitly need a change log?

For example, https://github.com/EthicalML/awesome-production-machine-learning/releases/tag/release-2024-03-01
image

@axsaucedo
Copy link
Collaborator Author

It's common practice, you can see most tools create this automatically, such as:

It's a nice to have as opposed to must have, so not something we'd need in the short term, but could be worth in the future - it's backwards compatible (ie tools create it fully historical file) so no rush either as it's idempotent when we choose to add.

@zhimin-z
Copy link
Collaborator

zhimin-z commented Nov 27, 2024

It's common practice, you can see most tools create this automatically, such as:

It's a nice to have as opposed to must have, so not something we'd need in the short term, but could be worth in the future - it's backwards compatible (ie tools create it fully historical file) so no rush either as it's idempotent when we choose to add.

Good idea, but it seems a bit over the top for this list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants