GitLab FOSS merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests2017-06-19T14:47:54Zhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10364Remove the IIFE's from files starting with G2017-06-19T14:47:54Zusername-removed-408881Remove the IIFE's from files starting with GThis MR only remove unnecessary IIFEs and convert some inline IIFEs to its `() => {}` equivalent.
**Affected files**
- app/assets/javascripts/gl_dropdown.js
- app/assets/javascripts/group_avatar.js
- app/assets/javascripts/groups_sel...This MR only remove unnecessary IIFEs and convert some inline IIFEs to its `() => {}` equivalent.
**Affected files**
- app/assets/javascripts/gl_dropdown.js
- app/assets/javascripts/group_avatar.js
- app/assets/javascripts/groups_select.js
- app/assets/javascripts/profile/gl_crop.js
- spec/javascripts/gl_dropdown_spec.js
- spec/javascripts/gl_field_errors_spec.js9.1https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9891Add a name field to the group edit form2017-06-19T14:47:54Zusername-removed-1181022Add a name field to the group edit form## What does this MR do?
Adds a text field to the group create and edit forms that enables edit of the group name.
Formerly the value of the name for the new or existing group was copied from the
value of the path.
I'm mentioning...## What does this MR do?
Adds a text field to the group create and edit forms that enables edit of the group name.
Formerly the value of the name for the new or existing group was copied from the
value of the path.
I'm mentioning @awhildy and @hazelyang from the issue thread to bring it to your attention.
Thanks to @smcgivern and @ClemMakesApps for mentoring help.
## Are there points in the code the reviewer needs to double check?
Ensure test coverage is sufficient and conforms to expectations.
## Why was this MR needed?
This satisfies a feature request in the backlog for community contribution to the community edition.
## Screenshots (if relevant)
![GroupNew](/uploads/c9f9d2f84ea806c27bfdc15592fd6d50/GroupNew.jpeg)
![GroupNewName](/uploads/0b2719f11d2c6565fda3cd06813a81d5/GroupNewName.jpeg)
![GroupEdit](/uploads/ecddd0997f9b581411094b8af4960555/GroupEdit.jpeg)
## Does this MR meet the acceptance criteria?
- [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [x ] Added for this feature/bug
- [x] All builds are passing
- [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if it does - 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?
[25474](https://gitlab.com/gitlab-org/gitlab-ce/issues/25474)https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10553Resolve "Performance issues when processing large build traces with Ansi2html"2017-06-19T14:47:53Zusername-removed-408881Resolve "Performance issues when processing large build traces with Ansi2html"Port of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10336 for `9-0-stable`
The original MR is based on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10311 so might be better to get that MR in `9-0-stable`first
r...Port of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10336 for `9-0-stable`
The original MR is based on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10311 so might be better to get that MR in `9-0-stable`first
ref: https://gitlab.com/gitlab-org/gitlab-ce/issues/305919.1https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10577Add field for group name2017-06-19T14:47:53Zusername-removed-408881Add field for group nameMR created just to check EE compatibility on CI, I'll delete if it passes.MR created just to check EE compatibility on CI, I'll delete if it passes.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10615Resolve "Performance issues when processing large build traces with Ansi2html"2017-06-19T14:47:53Zusername-removed-408881Resolve "Performance issues when processing large build traces with Ansi2html"Port of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10336 for `9-0-stable`
The original MR is based on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10311 so might be better to get that MR in `9-0-stable`first
ref: ...Port of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10336 for `9-0-stable`
The original MR is based on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10311 so might be better to get that MR in `9-0-stable`first
ref: https://gitlab.com/gitlab-org/gitlab-ce/issues/305919.1https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10702CE upstream - Friday2017-06-19T14:47:53Zusername-removed-128633CE upstream - FridayFiles to resolve:
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/716a2595fe5f2c3f503a3cc2b1be9f95c7b75a3f/app/assets/javascripts/boards/components/modal/footer.js
- [ ] @alfredo1 Please resolve https://gitla...Files to resolve:
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/716a2595fe5f2c3f503a3cc2b1be9f95c7b75a3f/app/assets/javascripts/boards/components/modal/footer.js
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/716a2595fe5f2c3f503a3cc2b1be9f95c7b75a3f/app/assets/javascripts/boards/components/sidebar/remove_issue.js
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/716a2595fe5f2c3f503a3cc2b1be9f95c7b75a3f/app/assets/javascripts/boards/stores/boards_store.js
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/716a2595fe5f2c3f503a3cc2b1be9f95c7b75a3f/spec/javascripts/lib/utils/text_utility_spec.js
Once the conflicts resolved, please push (no force-push!) to the `ce-to-ee-2017-04-14` branch.
Thanks in advance! ❤️
Note: This merge request was created by an experimental script, it's not perfect (yet)!username-removed-128633username-removed-128633https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10703CE upstream - Friday2017-06-19T14:47:53Zusername-removed-128633CE upstream - FridayFiles to resolve:
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/3570d4bd2c54a037f10fb9b531d593f6eedbe1a0/app/assets/javascripts/boards/components/modal/footer.js
- [ ] @alfredo1 Please resolve https://gitla...Files to resolve:
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/3570d4bd2c54a037f10fb9b531d593f6eedbe1a0/app/assets/javascripts/boards/components/modal/footer.js
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/3570d4bd2c54a037f10fb9b531d593f6eedbe1a0/app/assets/javascripts/boards/components/sidebar/remove_issue.js
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/3570d4bd2c54a037f10fb9b531d593f6eedbe1a0/app/assets/javascripts/boards/stores/boards_store.js
- [ ] @alfredo1 Please resolve https://gitlab.com/gitlab-org/gitlab-ee/blob/3570d4bd2c54a037f10fb9b531d593f6eedbe1a0/spec/javascripts/lib/utils/text_utility_spec.js
Once the conflicts resolved, please push (no force-push!) to the `ce-to-ee-2017-04-14` branch.
Thanks in advance! ❤️
Note: This merge request was created by an experimental script, it's not perfect (yet)!username-removed-128633username-removed-128633https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/11383Update singleton pattern docs in design_patterns.md2017-06-19T14:47:52ZLuke "Jared" BennettUpdate singleton pattern docs in design_patterns.md## What does this MR do?
Updates single pattern docs in design_patterns.md as suggest in a recent frontend call.
This change promotes "keep it simple".
## Are there points in the code the reviewer needs to double check?
## Why was th...## What does this MR do?
Updates single pattern docs in design_patterns.md as suggest in a recent frontend call.
This change promotes "keep it simple".
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [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 it does - 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?
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/320289.3Luke "Jared" BennettLuke "Jared" Bennetthttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/11416WIP: design_patterns.md DOM class manipulation2017-06-19T14:47:52ZLuke "Jared" BennettWIP: design_patterns.md DOM class manipulation## What does this MR do?
Update design_patterns.md DOM class manipulation to promote classes that aren't coupled to DOM in too specific ways and easy to test.
## Are there points in the code the reviewer needs to double check?
#...## What does this MR do?
Update design_patterns.md DOM class manipulation to promote classes that aren't coupled to DOM in too specific ways and easy to test.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [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 it does - 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?Luke "Jared" BennettLuke "Jared" Bennetthttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6124WIP: Redesign GitHub import view2017-06-19T11:14:10ZAchilleas PipinellisWIP: Redesign GitHub import view## What does this MR do?
Redesign the GitHub import view.
- Split into two columns, docs in the left, action in the right
- Add panel in the right column
- Use non-camelcase text
- Use the `settings-message` class to add the adm...## What does this MR do?
Redesign the GitHub import view.
- Split into two columns, docs in the left, action in the right
- Add panel in the right column
- Use non-camelcase text
- Use the `settings-message` class to add the admin note
- Link to user/admin docs
Inspired from the new protected branches views
https://gitlab.com/gitlab-org/gitlab-ce/tree/master/app/views/projects/protected_branches
## Are there points in the code the reviewer needs to double check?
Check that CSS classes are applied correctly. Is `settings-message` used correctly?
Also, I'm not sure about the button **List your GitHub repositories** having the same text in both cases for authentication.
The current scenarios are:
1. If the GitHub integration is enabled, you have two choices: either hit the green button directly, or provide a token and hit the button. The current functionality is that if I press **either** green button even without providing a token, it will perform the same action: take you to GitHub and authenticate.
1. If the GitHub integration is disabled, then we got only the second green button and the user **must** provide a token otherwise a 500 is shown. I think in this case we should check if the token field is filled by the user and show a warning otherwise.
## Why was this MR needed?
To make the import page prettier and add more information for the end user.
## Screenshots (if relevant)
### GitHub integration (oauth) disabled - before and after
![gh-import-integration-disabled-before](/uploads/536da65054009acd682b7383ee5c4191/gh-import-integration-disabled-before.png)
![gh-import-integration-disabled-after](/uploads/082af7826a8fbf59d8446dfcf86be5c8/gh-import-integration-disabled-after.png)
### GitHub integration (oauth) enabled - before and after
![gh-import-integration-enabled-before](/uploads/61346d5bf1a41783d9a374ae7cef204f/gh-import-integration-enabled-before.png)
![gh-import-integration-enabled-after](/uploads/635cbecdd250d684f420391382785012/gh-import-integration-enabled-after.png)
## 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 [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?
Needed for https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5987https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/11922Fixed the median display problem in the cycle analytics of i18n2017-06-19T09:55:28Zusername-removed-463743Fixed the median display problem in the cycle analytics of i18n## What does this MR do?
Fix the median display problem in multilingual periodic analysis.
see #33344
Contains all the files in [rails-i18n](https://github.com/svenfuchs/rails-i18n/tree/master/rails%2Flocale).## What does this MR do?
Fix the median display problem in multilingual periodic analysis.
see #33344
Contains all the files in [rails-i18n](https://github.com/svenfuchs/rails-i18n/tree/master/rails%2Flocale).https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12231Resolve "Missing translations for the project & repository pages" conflicts2017-06-19T07:35:16Zusername-removed-408677Resolve "Missing translations for the project & repository pages" conflictsWhen picking https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12052 into 9.3 RC3, there was a conflict.
```
Unmerged paths:
(use "git add <file>..." to mark resolution)
both modified: app/assets/javascripts/locale/en/a...When picking https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12052 into 9.3 RC3, there was a conflict.
```
Unmerged paths:
(use "git add <file>..." to mark resolution)
both modified: app/assets/javascripts/locale/en/app.js
both modified: app/assets/javascripts/locale/es/app.js
both modified: app/views/projects/pipeline_schedules/_form.html.haml
both modified: locale/en/gitlab.po
both modified: locale/es/gitlab.po
both modified: locale/gitlab.pot
```Bob Van Landuyt :neckbeard:Bob Van Landuyt :neckbeard:https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12258Update Prometheus Merge Request Metrics page2017-06-19T04:29:07ZJoshua LambertUpdate Prometheus Merge Request Metrics pageMinor updates to documentation.Minor updates to documentation.9.3https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12250Return fake application settings if we're in a Rake task and have migrations2017-06-17T22:30:12ZStan HuReturn fake application settings if we're in a Rake task and have migrations`master` was failing because `rake db:migrate` won't work if there are application settings that need to be migrated.`master` was failing because `rake db:migrate` won't work if there are application settings that need to be migrated.https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12216Add keydown_enter_search_input helper2017-06-16T22:07:00ZLuke "Jared" BennettAdd keydown_enter_search_input helper## What does this MR do?
Fix some transient issues pressing enter on the filtered search input in capybara w/ phantom.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if ...## What does this MR do?
Fix some transient issues pressing enter on the filtered search input in capybara w/ phantom.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [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 it does - 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?Luke "Jared" BennettLuke "Jared" Bennetthttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12210WIP: Resolve "Pipeline schedules callout has no top-margin"2017-06-16T14:21:55ZLuke "Jared" BennettWIP: Resolve "Pipeline schedules callout has no top-margin"## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](htt...## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [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 it does - 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?
Closes #33592https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12007Document the Delete Merged Branches functionality2017-06-16T11:19:02Zusername-removed-419655Document the Delete Merged Branches functionality## What does this MR do?
* Add documentation pages for `Branches`
* Adds a section related to the `Delete Merged Branches` button and it's limitations
## Are there points in the code the reviewer needs to double check?
## Why was this...## What does this MR do?
* Add documentation pages for `Branches`
* Adds a section related to the `Delete Merged Branches` button and it's limitations
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
A user was confused as to why protected branches were not deleted when this button was clicked
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [x] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [x] 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 it does - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #334459.4Achilleas PipinellisAchilleas Pipinellishttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/11902Add french translation of Cycle Analytics Page to I18N2017-06-16T06:40:19Zusername-removed-463743Add french translation of Cycle Analytics Page to I18N## What does this MR do?
Add `fr` of Cycle Analytics Page to I18N
Translation provided by @egeorget
Translation See #32998## What does this MR do?
Add `fr` of Cycle Analytics Page to I18N
Translation provided by @egeorget
Translation See #32998https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/11925WIP: Add French translations for Project and Repository pages2017-06-16T06:40:10Zusername-removed-517528WIP: Add French translations for Project and Repository pages## What does this MR do?
This MR add French translation for all translated page in the 9.3 milestone.
## Are there points in the code the reviewer needs to double check?
The translation still needs a second check, and some are s...## What does this MR do?
This MR add French translation for all translated page in the 9.3 milestone.
## Are there points in the code the reviewer needs to double check?
The translation still needs a second check, and some are still fuzzy. Still, I created this WIP merge request as a PoC and RFC for this feature
## Why was this MR needed?
In order to add French localisation to Gitlab.
## Screenshots
No screenshot yet, but **SOON**.
## Does this MR meet the acceptance criteria?
- [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [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 it does - 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 #32919
Closes #32998
Closes #33140 https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12202Update url for two_factor_authentication.md2017-06-16T02:54:36Zusername-removed-613973Update url for two_factor_authentication.md## What does this MR do?
Correct the url used for resetting 2fa recovery codes by ssh.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
The listed url was incorrect, the correct url was fou...## What does this MR do?
Correct the url used for resetting 2fa recovery codes by ssh.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
The listed url was incorrect, the correct url was found in Issue #3765.
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [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 it does - 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?