[informative, protocol] Branch master was rebased #8

New Issue

Closed

opened 2021-09-07 01:28:25 +02:00 by jotoho · 0 comments

jotoho commented

2021-09-07 01:28:25 +02:00

Owner

Today, I temporarily disabled branch protection on master to clean up a problem with the email addresses used by Gitea for commits issued in my name. This had the ramifications of changing all commit ids and effectively deleting the merge commits (the changes are still there) but I judged that to be acceptable considering the youth of the project and the fact, that I'm the only contributor.

This means that the tag of release v0.1.0 is now disconnected from the history of master but since the content is still the same, I'm inclined to tolerate that and simply make sure that future tags are on branch master. So don't be confused by Gitea saying that -2 commits were added to master since the release. It's just the deleted merge commits!

Today, I temporarily disabled branch protection on `master` to clean up a problem with the email addresses used by Gitea for commits issued in my name. This had the ramifications of changing all commit ids and effectively deleting the merge commits (the changes are still there) but I judged that to be acceptable considering the youth of the project and the fact, that I'm the only contributor. This means that the tag of release `v0.1.0` is now disconnected from the history of master but since the content is still the same, I'm inclined to tolerate that and simply make sure that future tags are on branch master. So don't be confused by Gitea saying that `-2` commits were added to master since the release. It's just the deleted merge commits!

jotoho added the