summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | | | Fix errors and grammarKatarzyna Kobierska2016-09-071-13/+10
| | | | | | |
* | | | | | | Fix rubocop errorsKatarzyna Kobierska2016-09-071-1/+1
| | | | | | |
* | | | | | | Change class method nameKatarzyna Kobierska2016-09-072-5/+5
| | | | | | |
* | | | | | | Add class method to encapsulate exceptionKatarzyna Kobierska2016-09-072-18/+25
| | | | | | |
* | | | | | | Move lint to api from ci/apiKatarzyna Kobierska2016-09-074-39/+39
| | | | | | |
* | | | | | | Add params requires to lintKatarzyna Kobierska2016-09-072-21/+21
| | | | | | |
* | | | | | | Fix rubocop testsKatarzyna Kobierska2016-09-071-2/+1
| | | | | | |
* | | | | | | Add tests for API CI LintKatarzyna Kobierska2016-09-072-16/+24
| | | | | | |
* | | | | | | API for CI LintKatarzyna Kobierska2016-09-073-0/+32
| |_|/ / / / |/| | | | |
* | | | | | Merge branch 'master' into feature/fork-to-group-apiOlaf Tomalka2016-09-063-18/+0
|\ \ \ \ \ \
| * | | | | | Clean up search result classesclean_up_search_classesValery Sizov2016-09-063-18/+0
| | |_|/ / / | |/| | | |
* | | | | | Higher code quality for fork to namespace APIOlaf Tomalka2016-09-061-1/+0
| | | | | |
* | | | | | Improved code quality on API fork namespace featureOlaf Tomalka2016-09-061-3/+6
| | | | | |
* | | | | | Added fork API paremeter for a specific namespaceOlaf Tomalka2016-09-061-2/+14
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Browser interface allows forking to an owned grup. This commit brings API up to speed by providing optional namespace parameter to fork API. This allows forking to users and groups under forker's control using their id or unique name. Fixes #21591
* | | | | Merge branch 'safe-ref-updates' into 'master' Douwe Maan2016-09-051-2/+2
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Safer ref updates Use `git update-ref` to prevent clobbering concurrent ref updates. If rugged/libgit2 is temporarily confused, due to concurrent `git gc` for example, then it used to be possible to accidentally reset a ref to an earlier state and lose commits. Because `git update-ref` does not get confused by `git gc`, what will happen now is that the commit based on confused information fails, preventing data loss. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/20353 See merge request !6130
| * | | | Use 'git update-ref' for safer web commitsJacob Vosmaer2016-09-021-2/+2
| | |_|/ | |/| |
* | | | Merge branch 'internal_recovery_api' into 'master' Douwe Maan2016-09-021-5/+9
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | Minor edits to two_factor_recovery_codes API error catching Minor fixes to the `two_factor_recovery_codes` internal API making the conditionals more sane. Thanks @DouweM for pointing it out. See merge request !6000
| * | | Minor edits to two_factor_recovery_codes API error catchingDrew Blessing2016-08-311-5/+9
| | |/ | |/|
* | | Merge branch 'issue_19734' into 'master' Douwe Maan2016-09-016-13/+24
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Project tools visibility level ## part of #19734 ![project_features_access_level](/uploads/81ec7185d4e61d7578652020209af925/project_features_access_level.png) ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [x] API support added - Tests - [x] Added for this feature/bug - [x] All builds are passing - [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 you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !5606
| * | | Project tools visibility levelFelipe Artur2016-09-016-13/+24
| | | |
* | | | Merge branch 'merge-request-sha-info' into 'master' Douwe Maan2016-09-011-0/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge request sha info ## What does this MR do? Exposes `sha` and `merge_commit_sha` items in `MergeRequest` API endpoint data. ## Are there points in the code the reviewer needs to double check? No. ## Why was this MR needed? It's useful information. ## What are the relevant issue numbers? Closes #20456. ## Screenshots (if relevant) N/A ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [x] API support added - Tests - [x] Added for this feature/bug - [x] All builds are passing - [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 you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !5966
| * | | | entities: expose {,merge_commit_}sha in MergeRequestBen Boeckel2016-08-311-0/+2
| | | | | | | | | | | | | | | | | | | | Fixes #20456.
* | | | | Merge branch 'js-tooltips-for-mentions' into 'master' Robert Speicher2016-09-016-15/+12
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use JavaScript tooltips for mentions ## What does this MR do? - use JavaScript tooltips instead of plain title for mentions (issue, merge request, snippet, user, group, commit, commit range, milestone) ## Why was this MR needed? JavaScript tooltips look nicer and can wrap. ## What are the relevant issue numbers? https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5261#note_13106713, fixes #21500 See merge request !5301
| * | | | | Use JavaScript tooltips for mentions (!5301)winniehell2016-09-016-15/+12
| | | | | |
* | | | | | GitHub importer use default project visibility for non-private projectsDouglas Barbosa Alexandre2016-08-311-1/+1
| |_|/ / / |/| | | |
* | | | | Merge branch 'refactor/add-policies' into 'master' Robert Speicher2016-08-313-12/+4
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Refactor ability.rb into Policies ## What does this MR do? Factors out `ability.rb` into a new abstraction - the "policy" (stored in `app/policies`). A policy is a class named `#{class_name}Policy` (looked up automatically as needed) that implements `rules` as follows: ``` ruby class ThingPolicy < BasePolicy def rules @user # this is a user to determine abilities for, optionally nil in the anonymous case @subject # this is the subject of the ability, guaranteed to be an instance of `Thing` can! :some_ability # grant the :some_ability permission cannot! :some_ability # ensure that :some_ability is not allowed. this overrides any `can!` that is called before or after delegate! @subject.other_thing # merge the abilities (can!) and prohibitions (cannot!) from `@subject.other_thing` can? :some_ability # test whether, so far, :some_ability is allowed end def anonymous_rules # optional. if not implemented `rules` is called where `@user` is nil. otherwise this method is called when `@user` is nil. end end ``` See merge request !5796
| * | | | use a nil subject when we want to check global abilitieshttp://jneen.net/2016-08-302-2/+2
| | | | |
| * | | | remove Ability.abilitieshttp://jneen.net/2016-08-302-6/+2
| | | | |
| * | | | remove six, and use a Set insteadhttp://jneen.net/2016-08-301-5/+1
| | | | |
* | | | | Add BroadcastMessage API implementationRobert Speicher2016-08-313-0/+105
| | | | |
* | | | | Merge branch ↵Robert Speicher2016-08-314-51/+16
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | '21567-fix-sorting-issues-by-last-updated-after-import-from-github' into 'master' Fix sorting issues by "last updated" after import from GitHub ## What does this MR do? Don't touch Issue/Merge Request when importing GitHub comments as it will trigger an update on `updated_at` field. It also use `updated_at` as the last updated date doesn't matter the Issue/Pull Request state. ## Why was this MR needed? After import from GitHub, sorting issues by "last updated" doesn't work as expected. ## What are the relevant issue numbers? Fixes #21567 See merge request !6110
| * | | | | Don't touch Issue/Merge Request when importing GitHub commentsDouglas Barbosa Alexandre2016-08-311-6/+8
| | | | | |
| * | | | | Use updated_at as the last updated date when importing from GitHubDouglas Barbosa Alexandre2016-08-313-45/+8
| | | | | |
* | | | | | Merge branch 'fix-sidekiq-sentry-context' into 'master' Robert Speicher2016-08-311-0/+27
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix Sentry not reporting right program for Sidekiq workers Moves program tag into the global configuration since this doesn't change and since Sidekiq workers get a unique context for each event. Closes #21410 See merge request !6004
| * | | | | Fix Sentry not reporting right program for Sidekiq workersfix-sidekiq-sentry-contextStan Hu2016-08-251-0/+27
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | Moves program tag into the global configuration since this doesn't change and since Sidekiq workers get a unique context for each event. Closes #21410
* | | | | Merge branch 'api-confidential-issues' into 'master' Robert Speicher2016-08-312-2/+13
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | API: Expose issue confidentiality flag. ## What does this MR do? This MR adds support for confidential issues the the API. The property as exposed and users can create or update confidential issues. ## What are the relevant issue numbers? Closes #17199 See merge request !5384
| * | | | | API: Expose issue#confidentialapi-confidential-issuesRobert Schilling2016-08-312-2/+13
| | |_|/ / | |/| | |
* | | | | Don't expose a user's private token in the `/api/v3/user` API.Timothy Andrew2016-08-311-1/+1
|/ / / / | | | | | | | | | | | | | | | | | | | | - This would allow anyone with a personal access token (even a read-only token, once scopes are implemented) to escalate their access by obtaining the private token.
* | | | Merge branch 'project-specific-lfs' into 'master' Robert Speicher2016-08-302-4/+10
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added project specific enable/disable setting for LFS ## What does this MR do? Adds project specific enable/disable setting for LFS ## What are the relevant issue numbers? Needed for #18092 See merge request !5997
| * | | | Renamed `enable_lfs` to `lfs_enabled` for the Project field, and related fixes.project-specific-lfsPatricio Cano2016-08-302-6/+8
| | | | |
| * | | | Added CHANGELOG, documentation, and API functionalityPatricio Cano2016-08-302-3/+7
| | | | |
* | | | | Merge branch 'prevent_authored_awardable_votes' into 'master' Robert Speicher2016-08-301-1/+5
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | prevent authored awardable thumbs votes ## What does this MR do? This MR should prevent users from upvoting or downvoting issues/merge requests/notes authored by them. ## What are the relevant issue numbers? Closes #20913 See merge request !5841
| * | | | Merge branch 'master' into prevent_authored_awardable_votesbarthc2016-08-305-8/+5
| |\ \ \ \ | | | |/ / | | |/| |
| * | | | prevent authored awardable thumbs votesbarthc2016-08-281-1/+5
| | |/ / | |/| | | | | | | | | | | | | | | | | | prevent authored awardable thumbs votes prevent authored awardable thumbs votes
* | | | Merge branch ↵Douwe Maan2016-08-301-16/+4
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | '19721-issues-created-through-api-do-not-notify-label-subscribers' into 'master' user is now notified when creating an issue through the api Previously when a issue was created through our API it would not mail label subscribers, this MR aims to fix that - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [x] API support added - Tests - [x] Added for this feature/bug - [x] All builds are passing - [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 you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) Closes #19721 See merge request !5720
| * | | if issue is not valid we revert back to the old labels when updatingtiagonbotelho2016-08-302-17/+2
| | | |
| * | | refactors update issue api request and some minor commentstiagonbotelho2016-08-302-16/+18
| | | |
| * | | adds test to check whether or not an email is sent to label subscribers ↵tiagonbotelho2016-08-301-19/+6
| | | | | | | | | | | | | | | | after creating a new issue through the api
| * | | user is now notified when creating an issue through the apitiagonbotelho2016-08-301-2/+16
| | | |
* | | | Merge branch 'artifacts-from-ref-and-build-name' into 'master' Douwe Maan2016-08-302-4/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a download buttons for Build Artifacts ## What does this MR do? This MR adds a download buttons for build artifacts of latest succesful pipeline in: - dashboard of project, - branches and tags views, - and tree viewer Implement #4255 ## What are the relevant issue numbers? Closes #4255, Closes #14419 ## Screenshots ### Project main ![](/uploads/29ee2154a214416059a875f2715d4fa3/Screen_Shot_2016-08-24_at_8.00.31_PM.png) ### Branches ![](/uploads/9220c593288370986fbc1d42a1425ef7/Screen_Shot_2016-08-24_at_8.02.01_PM.png) ### Tags ![](/uploads/a843e8103221fea475a0cf9d62a1999d/Screen_Shot_2016-08-24_at_8.03.32_PM.png) ### Source Tree ![](/uploads/63cd3c8c91b6f427c166dc90d8e3c059/Screen_Shot_2016-08-24_at_8.04.56_PM.png) ## Does this MR meet the acceptance criteria? - [x] [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) - [x] Download buttons - [x] Models - [x] Routes - [x] Projects::ArtifactsController - [x] API - Tests - Rails - [x] Project#builds_for - [x] branch name with slashes - [x] only success builds - [x] only latest builds - [x] feature tests for download buttons - API - [x] branch name with slashes - [x] only success builds - [x] only latest builds - [x] All builds are passing - [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 you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !5142
View Lorry Controller Status