22 Mar, 2014

1 commit

  • 3704d85b   Remove periods from merge request ... Browse File » 
    The "Merged by" and "Closed by" statements end with an extra space followed by a period. This doesn't seem necessary to me and not having the extra space followed by a period looks better to me. Also, the top of the merge request doesn't have the sentence ending with a period.
    awiddersheim
     

28 Feb, 2014

1 commit

27 Feb, 2014

1 commit

19 Feb, 2014

1 commit

18 Feb, 2014

4 commits

11 Feb, 2014

2 commits

31 Dec, 2013

1 commit

30 Dec, 2013

1 commit

24 Dec, 2013

1 commit

19 Dec, 2013

2 commits

14 Dec, 2013

1 commit

12 Nov, 2013

1 commit

  • dfb8d2b7   Improve status message on merge request page ... Browse File » 
    The status message currently looks like:

  Created on Oct 24, 2013 by John , currently assigned to Bob

There is a space between the author name and the comma, which is
incorrect.  Also, there is no period at the end of the sentence,
which makes it inconsistent with the following line:

  Merged by Bob 5 minutes ago.

Change it to:

  Created on Oct 24, 2013 by John.  Currently assigned to Bob.

Also change the milestone information from:

  and attached to milestone XYZ

to:

  Attached to milestone XYZ.
    David Pursehouse
     

23 Oct, 2013

1 commit

16 Oct, 2013

1 commit

09 Sep, 2013

1 commit

25 Aug, 2013

1 commit

  • c8a115c0   Link issues from comments and automatically close them ... Browse File » 
    Any mention of Issues, MergeRequests, or Commits via GitLab-flavored markdown
references in descriptions, titles, or attached Notes creates a back-reference
Note that links to the original referencer. Furthermore, pushing commits with
commit messages that match a (configurable) regexp to a project's default
branch will close any issues mentioned by GFM in the matched closing phrase.
If accepting a merge request would close any Issues in this way, a banner is
appended to the merge request's main panel to indicate this.
    ash wilson
     

23 Jun, 2013

1 commit