Click the associated tag:

> This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Glorious. Today of all days it would genuinely give me pause for caution.

Hopefully just a mistake? But looks like a botched release at the least

OJFord 3 hours ago | parent | next [-]

Same on the older few. I'm not sure I understand it though, seems strange you can have a tag for a commit that's only present in a fork?

Is it perhaps a bit misleading, and only means that there's no branch containing that commit?

	▲	CodesInChaos 2 hours ago \| parent \| next [-]
		There is little difference between a tag and a branch in git. There is just the convention that tags reference the same commit forever, while branches move. On github forks are part of the same physical repository. You could imagine that each logical repository is just a namespace for branches and tags, backed by the same physical repository. I do consider the warning a bug if github, it should check both tags and branches for commits which are to be considered part of a logical repository.
	▲	cyberclimb 3 hours ago \| parent \| prev \| next [-]
		It can mean either, it's a consequence of how github optimized their backend storage so a 100 forks of a repo initially take up the same space as 0 forks
	▲	drdec 3 hours ago \| parent \| prev [-]
		main (or master) is just another branch to git.

fixkitai 3 hours ago | parent | prev [-]

[flagged]