summaryrefslogtreecommitdiff
path: root/app/presenters
Commit message (Collapse)AuthorAgeFilesLines
* Display issue state in issue links section of merge request widget33381-display-issue-state-in-mr-widget-issue-linksAdam Niedzielski2017-06-091-2/+14
|
* Merge branch '3191-deploy-keys-update' into 'master'Rémy Coutable2017-06-071-11/+3
|\ | | | | | | | | | | | | Implement ability to update deploy keys Closes #3191 See merge request !10383
| * Implement ability to update deploy keysAlexander Randa2017-06-021-11/+3
| |
* | Use sum instead of map + injectAdam Niedzielski2017-06-021-1/+1
| |
* | Add Conversational Development Index page to admin panelTaurie Davis, Simon Knox and Adam Niedzielski2017-06-011-0/+144
|/
* Fix conflict resolution from corrupted upstreamfix-conflict-resolution-with-corrupt-reposSean McGivern2017-05-121-1/+5
| | | | | | | | | | | | | | | | | I don't know why this happens exactly, but given an upstream and fork repository from a customer, both of which required GC, resolving conflicts would corrupt the fork so badly that it couldn't be cloned. This isn't a perfect fix for that case, because the MR may still need to be merged manually, but it does ensure that the repository is at least usable. My best guess is that when we generate the index for the conflict resolution (which we previously did in the target project), we obtain a reference to an OID that doesn't exist in the source, even though we already fetch the refs from the target into the source. Explicitly setting the source project as the place to get the merge index from seems to prevent repository corruption in this way.
* Merge request widget redesignFatih Acet2017-05-091-0/+168
|
* Merge remote-tracking branch 'origin/29667-deploy-keys' into ↵Jacob Schatz2017-04-271-0/+11
|\ | | | | | | deploy-keys-load-async
| * Project deploy keys json end pointJarka Kadlecova2017-03-241-0/+11
| |
* | Also track auto-cancelling in jobs, detail:Lin Jen-Shin2017-04-062-3/+5
| | | | | | | | | | | | | | | | Not only tracking auto-cancelling in pipelines, we'll also track this in jobs because pipelines could be retried and the information would get lost when this happened. Also erase auto-cancelling relation for pipelines when they're retried.
* | Add test for presentersLin Jen-Shin2017-04-061-4/+0
| |
* | Fix test and only show job status title if it'sLin Jen-Shin2017-04-051-0/+6
| | | | | | | | cancelled and the pipeline is auto-cancelled.
* | rename pipeline_presenterRydkin Maxim2017-04-041-1/+1
| |
* | remove redundant `pipeline`Rydkin Maxim2017-04-041-1/+1
| |
* | add presenter for status badgeRydkin Maxim2017-04-041-0/+13
|/
* Added delegations to comply with the new rubocop rulesJose Ivan Vargas2017-03-061-12/+3
| | | | | Also fixed the deploy_keys view and moved the code from the repository_helper to the repository_controller
* Added tests for the repository_controller and repository_helperJose Ivan Vargas2017-03-061-0/+4
| | | | | | | | Added specs for the deploy_keys_presenter and added a new method in the presenter called #key_available? Fixed some minor UX inconsistencies and added a concern to handle redirection
* Introduced the deploy keys presenterGrzegorz Bizon2017-03-061-0/+65
|
* Don't override presentee methods for Gitlab::View::Presenter::DelegatedRémy Coutable2017-01-241-3/+3
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* More improvements to presenters23563-document-presentersRémy Coutable2017-01-184-28/+19
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix typos and improve presenters documentationRémy Coutable2017-01-181-39/+28
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Improve presenter architectureRémy Coutable2017-01-184-20/+24
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Document presentersRémy Coutable2017-01-183-0/+185
Signed-off-by: Rémy Coutable <remy@rymai.me>