allura-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cory Johns <cjo...@slashdotmedia.com>
Subject Re: Links to git commits
Date Tue, 02 Apr 2013 21:11:49 GMT
Jon,

The SCM tools currently require either 6 characters or the full commit
hash, so either [0fd58e] or [0fd58e050cd7d010b8146312eb4772ada928e030]
would work.  You can also use the text replacement style for the link so
that it doesn't appear so long.  For example,
[0fd58e](0fd58e050cd7d010b8146312eb4772ada928e030) would work and show up
as just 0fd58e.  (You could use
[\[0fd58e\]](0fd58e050cd7d010b8146312eb4772ada928e030) to include the
brackets and make the link show up as [0fd58e] to match other code
reference links.)

More information can be found in the Formatting Help under Artifact Links
(though be aware that cross-project links such as [allura:git:74dbc8] are
not currently implemented for the SCM tools).


On Tue, Apr 2, 2013 at 4:45 PM, David Brondsema <
dbrondsema@slashdotmedia.com> wrote:

>
>
> From: Jon Schewe <jpschewe@mtu.net>
> Date: Tue, Apr 2, 2013 at 7:49 AM
> Subject: Links to git commits
> To: allura-users@incubator.apache.org
>
>
> I noticed that if I put in my ticket comments [0fd58e0] the link doesn't
> get recognized, but if I used [0fd58e] it does. It seems that Allura is
> only looking for 6 characters, yet sometimes you need 7 to get the right
> hash. Is there a more explicit way of referencing a git commit so that I
> can specify a longer hash, but make it clear to Allura that this is
> referencing a git commit?
>
> --
> http://mtu.net/~jpschewe
>
>

Mime
View raw message