delta/gitlab/gitlab-ce.git/spec/helpers, branch 3870-commit-sorting-issue

Sanitize repo paths in new project error message

2016-05-04T21:06:07+00:00

Closes #17243

Merge remote-tracking branch 'dev/master' into 'master'

2016-05-02T23:58:54+00:00

Updated label links to work correctly for filtering

2016-04-26T08:13:03+00:00

See !3846#note_5033951

Ensure URL in all Service subclasses are valid

2016-04-25T19:28:24+00:00

Signed-off-by: Rémy Coutable

Fix license detection to detect all license files, not only known licenses

2016-04-25T08:31:28+00:00

Fixes #15470.

Signed-off-by: Rémy Coutable

Merge branch 'rs-diff_view' into 'master'

2016-04-22T07:49:46+00:00


Always read diff_view setting from the cookie

Prior, when the user had their view set to "parallel" and then visited a
merge request's changes tab _without_ passing the `view` parameter via
query string, the view would be parallel but the `Notes` class was
always instantiated with the default value from `diff_view` ("inline"),
resulting in broken markup when the form to add a line note was
dynamically inserted.

The cookie is set whenever the view is changed, so this value should
always be up-to-date.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/14557 and https://gitlab.com/gitlab-org/gitlab-ce/issues/15285

See merge request !3732

Merge branch 'ci-commit-as-pipeline' into 'master'

2016-04-21T08:10:37+00:00


Ci::Commit becomes a Pipeline object

1. Ci::Commit receives context: ref, :tag.
1. One Ci::Commit describes a one Pipeline
1. Pipeline is created from `.gitlab-ci.yml`
1. Pipeline is a ordered group of builds
1. We test MR against Pipeline
1. Pipelines have a separate view (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3703)
1. Pipeline can be triggered from UI (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3703)
1. Later we change `Trigger -> TriggerRequest -> Build` to `Trigger -> Pipeline` (future)
1. We add a Pipeline Hook that will be triggered on Pipeline status change  (future)
1. We extend notifications to use `Pipeline Hook` to send summary on pipeline changes (future)

After merging that I'll prepare a separate MR that will unify naming, database columns, table names:
```
Ci::Commit -> Pipeline
Ci::Build -> Build
CommitStatus -> Job
GenericCommitStatus -> ExternalJob

ci_commits -> pipelines
ci_builds -> jobs
```

This MR implements first 5 points.

This is made to solve this issue https://gitlab.com/gitlab-org/gitlab-ce/issues/14149.

See merge request !3653

Merge branch 'imported-ghe-project-names-links-to-github' into 'master'

2016-04-19T17:13:25+00:00


Fix GitHub project's link in the import page when provider has a custom URL

Closes gitlab-org/gitlab-ee#478

See merge request !3803

Fix GitHub project's link on import page when provider has a custom URL

2016-04-19T16:21:30+00:00

Remove persistent XSS vulnerability in `commit_person_link` helper

2016-04-17T22:42:49+00:00

Because we were incorrectly supplying the tooltip title as
`data-original-title` (which Bootstrap's Tooltip JS automatically
applies based on the `title` attribute; we should never be setting it
directly), the value was being passed through as-is.

Instead, we should be supplying the normal `title` attribute and letting
Rails escape the value, which also negates the need for us to call
`sanitize` on it.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/15126