diff options
| author | Fatih Acet <acetfatih@gmail.com> | 2016-09-21 15:11:13 +0000 |
|---|---|---|
| committer | Fatih Acet <acetfatih@gmail.com> | 2016-09-21 15:11:13 +0000 |
| commit | ab49c1a3a326ad44cc3481becf0cad9095205703 (patch) | |
| tree | 524a9906eeb2f762b4254870e4d68051cbfb87b0 /doc | |
| parent | 94bb16aeabb198b64f07890d8d0073890b7e5758 (diff) | |
| parent | bc08960bfd601229281f10348f97b30a6e005454 (diff) | |
| download | gitlab-ce-ab49c1a3a326ad44cc3481becf0cad9095205703.tar.gz | |
Merge branch 'correct-builds-pipeline-commit-header-to-build-header' into 'master'
Changed `Commit` to `Build` header on builds table
## What does this MR do?
As [discussed here](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6322#note_15511777) the pipeline table `Commit` headers should be `Pipeline`. This also should apply to build table headers.
## Are there points in the code the reviewer needs to double check?
/cc @tauriedavis
## Why was this MR needed?
UI consistency
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
See merge request !6402
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions