A lot of fixes refer to revisions/commits it would be nice to have better integration for easier linking/finding commits.

Submitted by chris melman on 3 January 2013 at 16:24

On 4 January 2013 at 11:46 Eelco Visser commented:

Do you have a concrete proposal for doing that?

On 4 January 2013 at 12:05 chris melman commented:

I guess it is not that easy, but could go together with integration of reposearch into this app.
If we have credentials to clone/checkout a repo we could use this information to get list of commits etc.

For github it would be possible to also get this information through webservices, but that would be a very limited approach

On 4 January 2013 at 13:00 Elmer van Chastelet commented:

Regex might be an option?

e.g. Introduce an entity LinkType, which is manageable by YG admins.

entity LinkType {
   name :: String
   pattern :: Text
   linkText :: Text  //might contain refs to groups in the pattern using $X , where X is an integer.

Furthermore, Project admins might enable/disable the LinkTypes that are available in YG (enable by default?).

This approach would add some overhead for displaying each issue description/comment/..any wikitext, which I don’t think is a big issue. On output of wiki text -> apply the LinkType regex replaces, replacing a LinkType pattern match with a wikitext link: [(LinkType.linkText)]($0).

On 4 January 2013 at 15:57 chris melman commented:

I guess indeed a simple addition would be some regex replace where you can give a regex to match and replace it with a link, however that would still make it harsh for integrating versioncontrol systems that don’t have a webfront.
And I would prefer a lookup possibilities as well, for svn numbers are pretty easy but this doesn’t work for git or mercurial.

I guess maybe the first thing should be to have some kind of page where you just have a list of commits kinda like the github page of commits of a project, or something like that.
A simple version of what project tools like trac or redmine offer.

Log in to post comments