delta/gitlab/gitlab-ce.git/spec/routing, branch 25264-ref-commit

Add nested groups support to the routing

2016-11-23T12:08:36+00:00

Signed-off-by: Dmitriy Zaporozhets

Fix 500 error when group name ends with git

2016-11-21T19:03:18+00:00

Signed-off-by: Dmitriy Zaporozhets

Fix 404 on some group pages when name contains dot

2016-11-21T10:41:44+00:00

Signed-off-by: Dmitriy Zaporozhets

Fix routing spec for group controller

2016-11-08T13:54:17+00:00

Signed-off-by: Dmitriy Zaporozhets

Merge branch 'dz-rename-user-routes' into 'master'

2016-10-17T18:47:46+00:00

Rename users routing from /u/:username to /users/:username for
consistency with other routes

Renames /u/:username to /users/:username

To follow consistency with other routes (like groups) and
UsersController name.
Now when you can use `/:username` for accessing user page there is no
need in shortcut like `/u/`

See merge request !6851

Fix 404 when group path has dot in the name

2016-10-16T09:49:23+00:00

Signed-off-by: Dmitriy Zaporozhets

Update users routing spec

2016-10-13T11:11:26+00:00

Signed-off-by: Dmitriy Zaporozhets

Merge branch 'atom-routes' into 'master'

2016-10-11T14:04:31+00:00


Allow browsing branches that end with '.atom'

## What does this MR do?

1. Simplify the regex capture in the routing for the CommitsController
   to not exclude the '.atom' suffix. That's a perfectly valid git
   branch name, so we shouldn't blow up if we get it.
2. Because Rails now can't automatically detect the request format, add
   some code to do so in `ExtractPath` when there is no path. This means
   that, given branches 'foo' and 'foo.atom', the Atom feed for the
   former is unroutable. To fix this: don't do that! Give the branches
   different names!

## Why was this MR needed?

Creating a branch or tag name ending in '.atom' would cause some 500s on that repo.

## What are the relevant issue numbers?

Closes #21955. Related to !5994.

See merge request !6750

Allow browsing branches that end with '.atom'

2016-10-11T12:31:12+00:00

We need to do two things to support this:

1. Simplify the regex capture in the routing for the CommitsController
   to not exclude the '.atom' suffix. That's a perfectly valid git
   branch name, so we shouldn't blow up if we get it.
2. Because Rails now can't automatically detect the request format, add
   some code to do so in `ExtractPath` when there is no path. This means
   that, given branches 'foo' and 'foo.atom', the Atom feed for the
   former is unroutable. To fix this: don't do that! Give the branches
   different names!

Catch any undefined API routing and return 400 Bad Request

2016-10-10T13:32:32+00:00

Signed-off-by: Dmitriy Zaporozhets