27 Aug, 2013
15 commits
-
Use "/commits/:sha/diff" as opposed to "/commit/:sha", keeping in line with existing api urls (e.g. "/projects/:id", etc.) Fix 500 error resulting from a diff api call with an invalid commit hash Move "/commits/:sha/blob" to "/blobs/:sha", leaving the old path for backwards compatibility. Add ability to get a single commit via "/commits/:sha"
-
When block user - remove it from joined groups Dont remove user from own resources (groups, users)
-
Fix project_id field in MergeRequest API
26 Aug, 2013
22 commits
-
Clear redis cache and precompile assets during update to 6.0. Fix #4874 #4840
-
As a consequence on the namespaces change from 5.4 to 6.0, after upgrade lots of links on the dashboard were not working (pointing to projects without the group part on the url). Also, after upgrading to 6.0-stable, the network (branch history) function does not work. The progress bar rotates forever, but the network graph cannot be generated. Clearing redis cache fixes those issues.
-
[#4821] - Fix some missing iids
-
You should update to 6.0 before proceed with update to higher version. So its no reason to keep old tasks any more. It should be still available in 6-0-stable but not in master
-
Feature: get the diff of a commit via API.
-
When that branch contain a '/' in the branch name. Fix for git over HTTP
-
Linking objects from GFM references
25 Aug, 2013
3 commits
-
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.
-
add link on realisation api for java client
