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.

Sign up for GitHub

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

Jump to bottom

version-changelog should support something like --to-tag to get changes between tags #24

Open
michaelbeaumont opened this issue Aug 3, 2023 · 8 comments
Open

version-changelog should support something like --to-tag to get changes between tags #24

michaelbeaumont opened this issue Aug 3, 2023 · 8 comments
Labels
kind/improvement Improvement on an existing feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@michaelbeaumont
Copy link

What happened?

This is mainly for https://github.com/kumahq/kuma/actions/workflows/release.yaml, which can be run with a release tag that isn't the newest commit on the branch.
@michaelbeaumont michaelbeaumont added triage/pending This issue will be looked at on the next triage meeting kind/improvement Improvement on an existing feature labels Aug 3, 2023
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Aug 7, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 6, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 6, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@michaelbeaumont michaelbeaumont removed the triage/stale Inactive for some time. It will be triaged again label Nov 6, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 5, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 5, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Feb 5, 2024
@jakubdyszkiewicz
Copy link

Triage: @michaelbeaumont what's the use case?

@jakubdyszkiewicz jakubdyszkiewicz added triage/needs-information Reviewed and some extra information was asked to the reporter and removed triage/accepted The issue was reviewed and is complete enough to start working on it labels Feb 5, 2024
@michaelbeaumont
Copy link
Author

which can be run with a release tag that isn't the newest commit on the branch.

IIRC it was that commits had come onto the release branch before the tag could be released and the tool was including those commits after the tag, until the head of the branch

@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/needs-information Reviewed and some extra information was asked to the reporter labels Feb 26, 2024
@slonka
Copy link
Contributor

slonka commented Feb 26, 2024 •
edited
Loading

If I got this right this is the example situation:

release-2.2 pointing to x and 2.2.8 is on x-3 and you want a changelog between 2.2.7 and 2.2.8

@michaelbeaumont
Copy link
Author

yep

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 27, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label May 27, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 26, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@bartsmykla bartsmykla removed the triage/stale Inactive for some time. It will be triaged again label Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/improvement Improvement on an existing feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@michaelbeaumont @slonka @jakubdyszkiewicz @bartsmykla @lukidzi