| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
These are not required because MySQL is not
supported anymore
|
|
|
|
| |
None of this code can be reached any more, so it can all be removed
|
|\
| |
| |
| |
| | |
Multiple pipeline support for Build status
See merge request gitlab-org/gitlab-ce!30828
|
| |
| |
| |
| |
| | |
Adds specs for testing the new behavior of specifying a pipeline when
POSTing a status.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This allows user to specify the pipeline ID
when several pipelines has been triggered
on the same branch and commit.
Signed-off-by: Gaetan Semet <gaetan.semet@renault.com>
|
|\ \
| | |
| | |
| | |
| | | |
API: Allow changing only ci_default_git_depth
See merge request gitlab-org/gitlab-ce!30888
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Use correct parent when committing in WebIDE
See merge request gitlab-org/gitlab-ce!29598
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When passing start_branch on committing from the WebIDE, it's possible
that the branch has changed since editing started, which results in the
change being applied on top of the latest commit in the branch and
overwriting the new changes.
By passing the start_sha instead we can make sure that the change is
applied on top of the commit which the user started editing from.
|
|/
|
|
|
| |
This MR refactor RedisCounter and WebIdeCommitsCounter
to be reused by other components.
|
|
|
|
| |
EE MR: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14598
|
|\
| |
| |
| |
| | |
CE Backport: Read and write User "Admin notes" via API
See merge request gitlab-org/gitlab-ce!30775
|
| |
| |
| |
| |
| |
| | |
This change adds the ability to read and
write admin notes for a user via the
USER API
|
| |
| |
| |
| |
| |
| | |
We're adding more redis base counters to the web ide and other
classes. We're refactoring this class in other to use the logic
in other places.
|
| |
| |
| |
| | |
Include released_at parameter
|
| |
| |
| |
| |
| | |
- Background migration for changing null values to false
- Set false as default value for private_profile DB column
|
| |
| |
| |
| |
| |
| | |
Currently the base64-encoded value of the push-to-secondary data is
saved in `api_json.log`, and this can easily be hundreds of
megabytes. We should filter this from the logs.
|
|\ \
| | |
| | |
| | |
| | | |
[CE] Upgrade to Rails 5.2
See merge request gitlab-org/gitlab-ce!30052
|
| |/
| |
| |
| | |
Updates changed method names and fixes spec failures
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Resolve "API support for group-level clusters"
Closes #55623
See merge request gitlab-org/gitlab-ce!30213
|
| |
| |
| |
| | |
This is basically a copy of the API for project clusters.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The current approach requires catching exceptions to handle these errors
and callers are already handling model validations so it seems more
appropriate. Also it seemed to convoluted to add this logic directly to
the model since the model needs to check too many possible associations
to determine whether or not there are more than one cluster since the
model doesn't know what it's being created on. Additionally we only
wanted to validate during create to avoid the risk of existing models
becoming invalid by many different edge cases.
|
| |
| |
| |
| |
| |
| | |
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Rename ProjectEntity to IssuableEntity
Closes #58275
See merge request gitlab-org/gitlab-ce!30217
|
| | | |
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Remove `FeatureConstrainer` call wrapping api endpoint
- Remove `Feature.enabled?(:graphql)` conditionals in back and frontend
- Modify graphql test to be graphql flag agnostic
- Remove api routing spec
- Remove frontend feature flag via `gon`
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
New API endpoint for merge request count
Updates all open tabs at the same time with one call
Restructured API response
API response changed to 401 if no current_user
Added API + JS specs
Fix for Static Check
Updated Count on Open/Close, Assign/Unassign of MR's
Checking if MR Count is refreshed
Added # frozen_string_literal: true to spec
Added Changelog
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.
After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Make Housekeeping button do a full garbage collection
Closes #63349
See merge request gitlab-org/gitlab-ce!30289
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously the Housekeeping button and API would use the counter of last
pushes to determine whether to do a full garbage collection, or whether
to do one of the less comprehensive tasks: a full repack, incremental
pack, or ref pack. This was confusing behavior, since a project owner
might have to click the button dozens of times before a full GC would be
initiated.
This commit forces a full GC each time this is initiated. Note that the
`ExclusiveLease` in `HousekeepingService` prevents users from clicking
on the button more than once a day.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63349
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The auto_devops object sometimes doesn't exists. We may need to create
it.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
We map the boolean to the string 'fetch' or 'clone', to be more
explicit.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
- issues_access_level
- repository_access_level
- merge_requests_access_level
- builds_access_level
- wiki_access_level
- snippets_access_level
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at
|
| |
| |
| |
| |
| |
| | |
https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| |\
| | |
| | |
| | |
| | | |
Remove N+1 queries in boards API
See merge request gitlab-org/gitlab-ce!29634
|
| | |
| | |
| | |
| | |
| | |
| | | |
- Add test for N+1 queries
- Add destroyable lists scope to Board and List
- Preload lists for both project and group boards
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To avoid having to specify an actual password to create users, admins
can now use the `force_random_password` parameter to let Devise generate
a password.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63826
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
[master] Fix MR head pipeline leak
See merge request gitlab/gitlabhq!3148
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Expose merge requests count based on user access
See merge request gitlab/gitlabhq!3157
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Count issues related merge requests based on user access level. And
issue can have related MRs from projects where user does not have
access so the number of related merge requests should be adjusted
based on user's ability to access the related MRs.
https://gitlab.com/gitlab-org/gitlab-ce/issues/59581
|