-
-
Notifications
You must be signed in to change notification settings - Fork 844
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
List of unreleased changes, not sure where they come from #992
Comments
I have a similar situation. Almost all new merged pull requests are listed under |
in my project:
auto-generate only work if I change the default branch to master, or add a tag to branch develop. I guess the auto-generate log will only fetch tags on the default branch. |
Tags and branches are separate concepts in git. What do you mean with add a tag to branch? |
I mean master is branch contains the tag. can use this command to check which branch contain tag: git branch --contains tags/ and in my project: master is the branch which contain tag for my project setup, Do you have any idea how to make it work? |
Getting something similar to this in this commit when running against github/view_component. Running against
It's of note that all changes listed there were introduced in v2.48.0, but I might be misunderstanding |
Make sure you can see the version tags when you are on the development branch. If you cannot then try merging in the tag using |
Describe the bug
https://github.com/zalando/logbook/blob/main/CHANGELOG.md shows a long list of unreleased changes.
But when I click on Full Changelog then Github correctly claims:
To Reproduce
No clue, to be honest.
I've seen this from the very beginning, since I'm using the generator.
Maybe there is something screwed up with my history?
(I switched from merge to squash a while ago. Maybe that's related?)
Expected behavior
In my situation, I'd expect no unreleased changes after pushing a release.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: