Stuart: Template cribbed from Blue Prism (well, I wrote it)

2016-09-13T10:22:37Z

Template cribbed from Blue Prism (well, I wrote it)

New page

<includeonly><span class="plainlinks">[https://dev.blueprism.com/gitlab/development/{{{2|automate}}}/commit/{{{1|}}} {{#ifeq:{{{2|automate}}}|automate|{{#ifeq:{{{showproject|{{{3|}}}}}}|yes|({{{2|automate}}})}}|{{#ifeq:{{{showproject|{{{3|}}}}}}|no||({{{2}}})}}}} commit {{{1|}}}]</span></includeonly><noinclude>
Creates a link to a commit in the current web frontend to our versioning repository.

== Usage ==
The mandatory first parameter is the commit ID to link to. A second optional parameter can specify a different project - by default, this will assume the <code>automate</code> project.

Partial IDs are allowed as long as the web URL supports - for git, they work fine - typically the first 6-8 digits of the SHA1 hash will suffice as a unique ID for the commit.

== Examples ==

To link to commit 4ebaad524 in automate :-
<nowiki>{{commit|4ebaad524}}</nowiki>
which results in: {{commit|4ebaad524}}

To link to commit fe3940b128 in the qacontrol repo, use:
<nowiki>{{commit|fe3940b128|qacontrol}}</nowiki>
which results in: {{commit|fe3940b128|qacontrol}}

This will not show the project name if the project is <code>automate</code>. You can force it to show it then by passing a <code>showproject=yes</code> parameter, eg.
<nowiki>{{commit|4ebaad524|showproject=yes}}</nowiki>
will output: {{commit|4ebaad524|showproject=yes}}

Equally, a parameter of <code>showproject=no</code> will override the outputting of the project in non-automate calls. For example:
<nowiki>{{commit|fe3940b128|qacontrol|showproject=no}}</nowiki>
will produce: {{commit|fe3940b128|qacontrol|showproject=no}}

</noinclude>

Template:Commit - Revision history

Stuart: Template cribbed from Blue Prism (well, I wrote it)