| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
* remove feature flag for admin settings
* remove feature flag for domain settings
|
| |
|
|
| |
Updates changed method names and fixes spec failures
|
| |\
| |
| |
| |
| |
| |
| | |
Add `db_spin` and refactor ChaosController
Closes #64425
See merge request gitlab-org/gitlab-ce!30559
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add specs for new endpoint to move multiple issues.
Add changelog entry
Just check the first issue for the ability to move / update
Add specs for exceeding limits and malformed requests
Changed name of shared examples
Change title of changelog entry
Use %i instead of %w
Check permission to update issue on project instead of board
Use admin_issue permission to check for issue move ability
Changed variable name to avoid shadow issue_params method
Rename route to bulk_move
Change route definition
Check permissions for each issue
Combine methods for parameters permit check
Remove extra context
Change description of context
Check param for type Array
Add unit tests to MoveService
Use before_action for permission check
Use set instead of let!
Use let's instead of set
|
| |
|
|
|
| |
This introduces the single stat chart component aside from
the area chart component
|
| |\
| |
| |
| |
| | |
Prepare cycle analytics for group level
See merge request gitlab-org/gitlab-ce!30356
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- 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`
|
| |/
|
|
|
|
|
|
| |
This is a port MR for CE
Original MR:
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14141
|
| |
|
|
|
|
|
| |
We can now share project so that we don't have to load project twice.
Also, this extracts non-relevant logic out of Deployment.
Update DeploymentsController accordingly
|
| |\
| |
| |
| |
| |
| |
| | |
Create private merge requests in forks
Closes #58583
See merge request gitlab-org/gitlab-ce!29984
|
| | |
| |
| |
| | |
https://gitlab.com/gitlab-org/gitlab-ce/issues/58583
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Allow asynchronous rebase operations to be monitored
Closes #54117
See merge request gitlab-org/gitlab-ce!29940
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, we label items to be done as "Todo." This is grammatically
incorrect and (therefore) confusing—especially to our Spanish-speaking
users for whom "todo" has a specific and unrelated meaning.
We should use "To Do" and always use it as singular (not "To Dos").
Updates to wording in a few places per MR (ee) discussion
Updating locale/gitlab.pot
Updates to wording in a few places per MR (ee) discussion
Updating locale/gitlab.pot
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
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
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This new attribute is optional and used when set instead of the default
format `gitlab+deploy-token-#{id}`.
Empty usernames will be saved as null in the database.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/50228.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Includes changes to the Vue container registry component to support
the display of an empty message and error message when invalid
characters are found in the group, project or branch name.
repositories/index.html.haml has been changed to remove the content
and place into Vue component.
|
| | |
| |
| |
| |
| |
| | |
The /admin panel will now always return an uncached
application setting to ensure it always has the most
current info.
|
| | |\
| | |
| | |
| | |
| | | |
Add new onboarding to flipper A/B testing
See merge request gitlab-org/gitlab-ce!30125
|
| | | |
| | |
| | |
| | |
| | | |
Check if we're gitlab.com and the
:user_onboarding feature flag is enabled.
|
| | | |
| | |
| | |
| | | |
This reverts commit 4bed2daef935bb4097988e0eff4830fc13a23c37.
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
Support creating an MR/branch on a fork from an issue
See merge request gitlab-org/gitlab-ce!29831
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
If user can update an issue under the specified confidential
issue project, should be able to find the project.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When `confidential_issue_project_id` is set and the issue is
under that project, create the a note about branch creation
in that project. If not, do nothing.
When creating `new_merge_request` system note, set the project
where the MR will be referenced from so it'll be linked to when
the MR is created in another project.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Accept a `confidential_issue_project_id` param which will
be used for the system note target.
This also includes some refactoring on the spec to use
shared examples.
|
| | | | | |
|
| | |\ \ \
| | |/ /
| |/| |
| | | |
| | | | |
Add endpoint for fetching diverging commit counts
See merge request gitlab-org/gitlab-ce!29802
|
| | | | |
| | | |
| | | |
| | | | |
Extract diverging_commit_counts into a service class
|
| | |\ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
Extract MR's widget into a separate request
Closes #62723
See merge request gitlab-org/gitlab-ce!29979
|
| | | |/
| | |
| | |
| | |
| | |
| | | |
This commits extracts /merge_requests/1.json?serializer=widget
Into a separate /merge_requests/1/widget.json endpoint
This will allow to use caching for this request
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Now we have terminals for instance and group clusters we can remove the
FF now. Deploying to group clusters has been working without complaints
too.
|
| |\ \ \
| |/ /
|/| | |
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
Persist tmp snippet uploads at users
See merge request gitlab/gitlabhq!3138
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It persist temporary personal snippets under
user/:id namespaces temporarily while creating
a upload record to track it. If an user gets removed
while it's still a tmp upload, it also gets removed.
If the tmp upload is sent, the upload gets moved to
personal_snippets/:id as before. The upload record
also gets updated to the new model type as well.
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Ability to write a note in a private snippet
See merge request gitlab/gitlabhq!3133
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In the Snippets::NotesController the noteable was resolved and
authorized through the :snippet_id, so by passing a :target_id for a
different snippet it was possible to create a note on a snippet
where the user would be unauthorized to do so otherwise.
This fixes the problem by ignoring the :target_id and :target_type from
the request, and using the same noteable for creation and authorization.
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
into 'master'
Guests can know whether merge request template name exists or not
See merge request gitlab/gitlabhq!3117
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Previously, if a user was a guest member of a private project, they
could access the merge request template as we were not checking
permission-levels of the user.
When a issue template is asked for, the user must have :read_issue for
the project; or :read_merge_request when a merge request template is
asked for.
We also now rescue_from FileNotFoundError and handle as 404. This is
because RepoTemplateFinder can raise a FileNotFoundError exception,
which Rails previously handled as a 500.
Handling these in a way that is consistent with
ActiveRecord::RecordNotFound exceptions, within controllers that
inherit from Projects::ApplicationController at least, and returning a
404.
https://gitlab.com/gitlab-org/gitlab-ce/issues/54943
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Enable Gitaly ref caching for SearchController
See merge request gitlab-org/gitlab-ce!30105
|
| | |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
As we noticed in
https://gitlab.com/gitlab-org/gitlab-ce/issues/56627#note_185828742,
clicking on the "Issues" tab often requests the same reference in
rendering Markdown.
|
| |\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
Move Multiple Issue Boards for Projects to Core
See merge request gitlab-org/gitlab-ce!29757
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Refactor code to allow multiple issue boards management for projects
in CE
|
