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
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.
It also doesn't show that it's referenced by a tag. I'm pretty sure that until recently, it would show that the commit is referenced by a tag. The way this works is that we have a script making a temporary branch and committing a revision-based repo manifest, which it then tags.
1
1
So, this is pretty weird. They're making it seem like a commit referenced by a (signed) tag is concerning and may belong to a fork. It's not an orphaned object.
I'm pretty convinced that this would show the tag referencing it even a few weeks ago.
It doesn't really matter.
1