Template:GitCommit/doc

Template to link to commits in GIT, useful for writing release notes.

Long SHAs are automatically shortened.

Commit in blender/blender:

Explicit Fork & Repo References
An explicit repository name and commit hash is the recommended way to create links to commits, as it is reasonably un-ambiguous:

Commit in blender/blender:

Commit in blender/blender-addons:

Commit in blender/blender-addons-contrib:

For organizations different than the default Blender one, or for forks, a third parameter can be provided:

Commit in studio/flamenco:

Commit in mont29/blender:

Phabricator-like References
The  format as it existed in Phabricator is still supported for git repositories:

Commit in blender/blender:

Commit in blender/blender-addons:

Commit in blender/blender-addons-contrib:

It will remap to the proper organization when needed:

Commit in studio/flamenco:

This used to works for svn commits, however with Gitea, svn repositories are not exposed that way anymore, so an invalid link is generated:

Commit  in blender manual:

See Template:GitCommit/PhabricatorParse for more details.

Commit Hash Only
With only a commit hash parameter, this template creates a link to the main official Blender repository:

Commit in blender/blender:

Other References
Some other types of references are only supported for historical reasons and should never be used in new wiki text, see Template:GitCommit/PhabricatorParseDeprecated for details.