02 Oct, 2013

1 commit

  • Labels are saved in the database with the case they were originally created with.
    Before this change if a user created a label with the same text but different case
    the label would use the original case and no new label would be created in the
    database. With this change, labels are now case-sensitive.
    
    Steps to test:
    
    1. Before this change, create a new issue with a new label "FIxMe"
    2. Edit the issue and change the label to "FixMe"
    3. Note that the label reverted to "FIxMe"
    4. Apply this change
    5. Edit the issue again and change the label to "FixMe"
    Note that the new case was preserved. If you also look in the database in the "tags" table you will see that both labels are present - "FIxMe" and "FixMe".
    Drew Blessing
     

01 Oct, 2013

4 commits


30 Sep, 2013

1 commit


26 Sep, 2013

1 commit


25 Sep, 2013

5 commits


24 Sep, 2013

2 commits


22 Sep, 2013

1 commit


17 Sep, 2013

1 commit


14 Sep, 2013

1 commit


12 Sep, 2013

1 commit


11 Sep, 2013

5 commits


09 Sep, 2013

2 commits


07 Sep, 2013

1 commit

  • Previously, only number of changed files mattered. Now, number of lines to render in the diff are also taken into account.
    
    A hard limit is set, above which diffs are not rendered and users are not allowed to override that. This prevents high server
    resource usage with huge commits.
    
    Related to #1745, #2259
    
    In addition, handle large commits for MergeRequests and Compare controllers.
    
    Also fixes a bug where diffs are loaded twice, if user goes directly to merge_requests/:id/diffs URL.
    Boyan Tabakov
     

04 Sep, 2013

2 commits


02 Sep, 2013

1 commit


29 Aug, 2013

1 commit


27 Aug, 2013

5 commits


25 Aug, 2013

1 commit

  • 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
     

22 Aug, 2013

1 commit


21 Aug, 2013

3 commits