-
Notifications
You must be signed in to change notification settings - Fork 4
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
Issues with version bump script #53
Comments
The next weird thing is that the release branch was created in my fork, so I'm not able to create a release off of that. (I think I ought to be able to manually work around that.) |
One other thing that is odd, but I don't think we can do anything about, is that v0.4.1...v0.5 shows the fixes that were done between v0.4.0 and v0.4.1. It makes sense that it shows the commits (they were made in both main and the servicing branch), but what I really don't get is why it also shows the changes to the source files. |
Another weirdness: GitHub's "Auto-generate release notes" generates "What's Changed" with everything since the beginning of time. |
It sounds like this script only works if you clone from this repo as your origin, which you can do as a collaborator, FWIW. That's probably not optimal for how you normally hack on this though :/ I suspect your last two comments are related. I don't know how GitHub wants me to release cuts, but apparently the seemingly normal way I'm doing it isn't it. |
It looks like GitHub lets you pick a tag now to generate notes off of, and that actually works (although auto doesn't). |
I ran the version bump script, and a couple confusing things happened.
Quick background: on my working copy
upstream
issdwilsh/siobrultech-protocols
andorigin
isjkeljo/siobrultech-protocols
.HEAD
was onupstream/main
, it branched fromorigin/main
for the version bump. I hadn't updated that branch in a while, so it thought that 3.0 was the correct next release.jkeljo
I'm going to clean up what it did to my fork, update my
main
branch and try again. Will report back if I run into anything else.The text was updated successfully, but these errors were encountered: