GitHub added a warning to the display of commits not belonging to any branch on a repository. It's a workaround for how they add commits from pull requests to the repository where they're being proposed. Makes sense but not a solution for this.
However... they forgot about tags.
Conversation
Replying to
So, you get a concerning warning for a commit that is referenced via a tag but not a branch. This is normal. For example, when we tag our stable releases, we need to tag a manifest referring to the other repositories. It's part of the tagged release and is an immutable object.
1
4
There's no reason for us to push a branch with the manifest containing the revisions of all the other repositories. It would require creating a branch for every tagged release. The newest commit is always specific to the tagged release. Oh well, now there are annoying warnings...
5
Replying to
The message has been there for a good while, and they still maintain that the pull request thing is not a bug. It's not necessarily a warning (since they don't acknowledge the problem), but an explanation for why a branch name isn't there.
1
So for example, look at this typical commit:
github.com/GrapheneOS/har
It shows the branches and tags referencing it.
Look at this tag for our latest stable release manifest:
github.com/GrapheneOS/pla
Click through to the commit:
github.com/GrapheneOS/pla
It shows a warning.
1
1
Show replies