It would be nice if there was a scheme of references that would be recognized and linked accordingly by Gitlab.
It would be quite useful and its application would be quite universal.
Github's GitHub Flavored Markdown would probably be a good start for an idea on how to implement such a feature.
1234567 would link to commit 1234567
@foo would link to the respective user
!123 would link to a issue
#123 would link to a merge request
[foo] would link to the wiki page
&foo would link to/embed an attachment
$foo would link to/embed a snippet
"Fixes !123" in a commit message
"This has already been fixed by @foo in #123" in an issue note
"You should ask @foo" in a note
"Installation instructions have been updated accordingly in [Install_on_Windows]" in an issue note
"RTL layout is borked (see &1234567_rtl_layout_fail.jpg)" in an issue
"Then use the database update script $db_update.sh" in a wiki page or an issue note
... use your imagination ;)
+1 for this.
+1 would be great
+1 for this, would be really helpful
I prefer #123 for issues and !123 for merge requests, as we mantain compatibily with github and people don't get messed when switching.
👍 I agree with @kitop, use #[0-9]+ for issues and ![0-9]+ for merge requests.
Would love that too!
since #1183 you can use Github Flavored Markdown to link to
For now it will just show a tooltip with some info about the linked item when hovering over the link.
Also thanks to #1198 previews are available while editing. :)
So between @jaypikay's [https://github.com/gitlabhq/gitlabhq/issues/1170#issuecomment-7933408] comment on #1170
and #1183 you can get very close to github and redmine on this
Nice work guys!
Can't wait until this feature makes it in.
Let me know if anyone needs a tester. I've got it running on postgres also
+1 on this!
@riyad What's so complicated about linking to a commit with a note?
We can add a note like this: "commit (SHA) MESSAGE" or something like that. The only problem I see is when the commit author is not a Gitlab user.
related: #2161, #2169
Closing this ... anything beyond the current state deserves a separate issue.
if the developers open up more functionality for the PUT Api call.. i can get this whole commiting with refs , fixes done in a day.
API call to write comment on an issue,
API call to pass the userid instead of their key
would be the basic
Issue references are a planned feature, see http://gitlab.uservoice.com/forums/176466-general/suggestions/3692754-linking-issue-references
Available in GitLab 6.1
By the way, you can customize the pattern in https://gitlab.com/gitlab-org/gitlab-ce/blob/6-4-stable/config/gitlab.yml.example#L68
By default the pattern can be anywhere in the commit message, it doesn't need to be at the start anymore.
I would like to cite wiki pages in issues. I don't see how unless I link the FULL URL.
@inetbiz Yes, you need the full url
Merge branch 'remove-annoying-i18n-deprecation' into 'master'
Remove annoying i18n deprecation
Thanks to this guy http://stackoverflow.com/a/20381730
See merge request !197