| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Previously we asked a user to enter a new slug before taking them to
the Create Page page.
As a UX improvement, we now take them to a randomly generated URI so
they can begin creating their new page.
https://gitlab.com/gitlab-org/gitlab-ce/issues/46299
|
| |\
| |
| |
| |
| |
| |
| | |
Resolve "Multi selection for delete on registry page"
Closes #24705
See merge request gitlab-org/gitlab-ce!30837
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Remove duplicate -/users/terms routes
See merge request gitlab-org/gitlab-ce!31812
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
CE-specific changes for:
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/15129
Co-Authored-By: Alex Kalderimis <akalderimis@gitlab.com>
Co-Authored-By: Luke Duncalfe <lduncalfe@eml.cc>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Splits auto-refreshing of MR widget into 2 requests:
- the one which uses etag-caching and invalidates the fields on change
- the one without caching
The idea is to gradually move all the fields to etag-cached endpoint
|
| | | |
|
| | | |
|
| |/
|
|
| |
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14741
|
| |\ |
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | | |
Drop feature to take ownership of a trigger token
Closes #2868
See merge request gitlab/gitlabhq!3198
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removing API and frontend interactions that allowed
users to take ownership of a trigger token.
Removed mentions from the documentation.
|
| |/ /
| |
| |
| | |
https://gitlab.com/gitlab-org/gitlab-ce/issues/19186
|
| | |
| |
| |
| |
| |
| |
| | |
Extend the support for "X-Profile-Token: <token>" to have an additional
header that defines type of profile we are looking for, like:
X-Profile-Mode: execution
X-Profile-Mode: memory
|
| |/
|
|
|
|
| |
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
| |
|
|
|
|
|
|
| |
- 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`
|
| |\ |
|
| | |\
| | |
| | |
| | |
| | | |
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
|
| |\ \ \
| |/ /
|/| | |
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
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.
|
| | |\ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
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
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
CE-EE parity for routes
See merge request gitlab-org/gitlab-ce!29994
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
This ensures all routes are defined in both CE and EE, with EE-specific
routes being wrapped in `Gitlab.ee` blocks.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
Also release `u` from TOP_LEVEL_ROUTES
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add ability to reorder issues
See merge request gitlab-org/gitlab-ce!29012
|
| | | | |
| | | |
| | | |
| | | | |
to support manual sorting on the frontend
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Updating multiple application settings panels through
a single action causes the incorrect action to be shown
when there are errors. Instead, make each panel action
handle both updating and display.
|
| | |/
|/|
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We have one auto merge strategy today - Merge When Pipeline
Succeeds.
In order to add more strategies for Merge Train feature,
we abstract the architecture to be more extensible.
Removed arguments
Fix spec
|
| |\
| |
| |
| |
| | |
Move some project routes under - scope
See merge request gitlab-org/gitlab-ce!28830
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Affected project routes are:
* services
* boards
* releases
* forks
* group_links
* import
* avatar
* labels
* milestones
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| |
| |
| |
| |
| | |
- Select notification email by walking up group/subgroup path
- Add settings UI to set group email notification address
- Add tests
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This sets up all the basics for importing Phabricator tasks into
GitLab issues.
To import all tasks from a Phabricator instance into GitLab, we'll
import all of them into a new project that will have its repository
disabled.
The import is hooked into a regular ProjectImport setup, but similar
to the GitHub parallel importer takes care of all the imports itself.
In this iteration, we're importing each page of tasks in a separate
sidekiq job.
The first thing we do when requesting a new page of tasks is schedule
the next page to be imported. But to avoid deadlocks, we only allow a
single job per worker type to run at the same time.
For now we're only importing basic Issue information, this should be
extended to richer information.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
| |
Affected routes are:
* autocomplete_sources
* project_members
* deploy_keys
* deploy_tokens
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
|
|
|
|
| |
For settings, branches and tags
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|