summaryrefslogtreecommitdiff
path: root/lib/api/events.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42GitLab Bot2020-10-211-1/+1
|
* Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot2020-07-201-1/+1
|
* Add new api class for projects eventsMaƂgorzata Ksionek2019-04-241-47/+2
| | | | | | | | | | | | Refactor api events class to use external helper Move specs from old class Add changelog and magic string Refactor events class to be more explicit Remove blank line
* Hide confidential events in rubyBob Van Landuyt2018-12-171-30/+12
| | | | | | | | | | | | We're filtering the events using `Event#visible_to_user?`. At most we're loading 100 events at once. Pagination is also dealt with in the finder, but the resulting array is wrapped in a `Kaminari.paginate_array` so the API's pagination helpers keep working. We're passing the total count into that paginatable array, which would include confidential events. But we're not disclosing anything.
* Fix API::Namespaces to accept namepaces with dotsif-52811-fix_namespaces_api_routingImre Farkas2018-11-281-1/+1
| | | | | It also renames the API::PROJECT_ENDPOINT_REQUIREMENTS constant to API::NAMESPACE_OR_PROJECT_REQUIREMENTS
* Merge remote-tracking branch 'dev/master'Bob Van Landuyt2018-10-011-3/+19
|\
| * Redact events shown in the events APINick Thomas2018-09-211-3/+19
| |
* | Enable frozen string in lib/api and lib/backupgfyoung2018-09-291-0/+2
|/ | | | | | | | | | Partially addresses #47424. Had to make changes to spec files because stubbing methods on frozen objects is a mess in RSpec and leads to failures: https://github.com/rspec/rspec-mocks/issues/1190
* Disable existing offenses for the CodeReuse copsYorick Peterse2018-09-111-0/+8
| | | | | This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
* Add authenticate to events api. fix #49255Warren Parad2018-08-161-0/+5
|
* Eliminate N+1 queries with authors and push_data_payload in Events APIStan Hu2018-06-051-0/+1
|
* API: Use defined project requirementsrs-api-use-project-requirementsRobert Schilling2017-08-311-1/+1
|
* Accept a username for User-level Events APIMark Fletcher2017-06-061-2/+2
|
* Introduce an Events APIMark Fletcher2017-06-061-0/+86
* Meld the following disparate endpoints: * `/projects/:id/events` * `/events` * `/users/:id/events` + Add result filtering to the above endpoints: * action * target_type * before and after dates