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

Group PRs in release notes based on labels #160

Merged
merged 2 commits into from
Sep 16, 2024
Merged

Conversation

msschwartz21
Copy link
Collaborator

Prettier release notes :) Not sure how to test it until we run a release

@DragaDoncila
Copy link
Collaborator

@msschwartz21 I think we could test by tagging a release candidate, so you could tag v0.1.2rc0 instead of just v0.1.2. This will go through the full release workflow (including generating release notes), but users installing traccuracy would still get v0.1.1 unless they run pip install --pre traccuracy. If we're not happy with the format we can keep bumping the rc, and then when we are happy, we just tag v0.1.2 and run the full release.

Copy link
Collaborator

@DragaDoncila DragaDoncila left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving optimistically and we can edit once we release an rc!

@msschwartz21 msschwartz21 merged commit 2f38c1b into main Sep 16, 2024
13 checks passed
@msschwartz21 msschwartz21 deleted the release-notes branch September 16, 2024 19:02
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

Successfully merging this pull request may close these issues.

2 participants