| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
In order to implement https://gitlab.com/gitlab-org/gitlab-ee/issues/10179
we need several modifications on the CI config file. We are
adding a new ports section in the default Image object.
Each of these ports will accept: number, protocol and name.
By default this new configuration will be only enabled in
the Web IDE config file.
|
| |\
| |
| |
| | |
jarv/dev-to-gitlab-2019-04-02
|
| | |\
| | |
| | |
| | |
| | | |
Return cached languages if they've been detected before
See merge request gitlab/gitlabhq!2998
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Domain was introduced on 11.8 and was not included on the
Project Cluster API. With this change user will be able to include
domain when adding and updating a cluster. Domain will also be included
on the GET calls.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59441
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24034 introduced
a regression where only the first 20 branches were used to determine
whether a branch has been merged because the pagination was applied
incorrectly. Requesting the second page of branches via the API would
always have the wrong merge status. We fix this by properly paginating
the branches before requesting their merge status.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56250
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Prepares suggestion implementation for multi-line support
See merge request gitlab-org/gitlab-ce!26057
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds the groundwork needed in order to persist multi-line suggestions,
while providing the parsing strategy which will be reused for the
**Preview** as well.
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Allow multiple repositories per project
See merge request gitlab-org/gitlab-ce!26539
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This changes the repository type from a binary `wiki?` to a type. So
we can have more than 2 repository types.
Now everywhere we called `.wiki?` and expected a boolean, we check
that type.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Backport EE API parameters in lib/api
See merge request gitlab-org/gitlab-ce!26369
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This backports the EE specific parameters for API::Parameters, wrapping
them in a conditional.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This backports the EE specific parameters for API::Users, and wraps them
in a conditional.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This backports the API parameters from API::Settings that were added in
EE, wrapping them in a conditional.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This backports EE specific parameters EE adds to API::ProtectedBranches,
and wraps them in a conditional.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This backports various parameter changes EE makes to API::Projects,
along with moving some code around to make it easier to extend in EE.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This backports the parameters that EE adds to API::Issues, and wraps
them in conditionals so they are only used in EE.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This backports all changes made to this module in EE to CE, and wraps EE
specific code in a conditional.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This backports the API parameters for API::Groups from EE to CE,
ensuring both implementations use the same code. EE specific parameters
are wrapped in an `if` statement for two reasons:
1. It allows us to completely disable the parameters in CE.
2. It removes the need for adding a source comment to signal that the
parameters are EE only.
|
| |/ / |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
due to the usage in EE this attempt to more DRYness is not worth it.
|
| | |
| |
| |
| |
| |
| | |
as the params block is evaluated when loading the class and the db
connection is not available yet we can't use the feature toggle inside
that block.
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Resolve CE to EE differences in the lib/api directory
See merge request gitlab-org/gitlab-ce!25430
|
| | |
| |
| |
| |
| | |
This allows EE to customize the parameters used in two places, without
having to modify the source code directly.
|
| | |
| |
| |
| |
| | |
This backports a line from EE so that both the CE and EE code are
identical.
|
| | |
| |
| |
| |
| | |
This refactors API::Settings so that EE can more easily extend its
behaviour, without having to modify the CE source code directly.
|
| | |
| |
| |
| |
| |
| |
| | |
This moves various constants previously defined in API::Services to the
API::Helpers::ServicesHelpers module, using class methods instead of
constants. This allows EE to extend the returned values, without having
to modify the CE source code directly.
|
| | |
| |
| |
| |
| | |
This refactors API::Search so that Enterprise Edition can more easily
extend its functionality, without having to modify the file directly.
|
| | |
| |
| |
| |
| |
| | |
This moves API::ResourceLabelEventsHelpers::EVENTABLE_TYPES to a class
method in a separate helper module, allowing EE to redefine it without
having to directly modify the source code.
|
| | |
| |
| |
| |
| |
| | |
This adds a method to API::Internal that returns the URL to use for LFS
authentication tokens. This makes it possible for EE to redefine this
behaviour, without having to directly modify the source code.
|
| | |
| |
| |
| |
| |
| | |
Similar to creating groups in the groups API, EE injects custom code
just before we update an existing group. Moving the update logic to a
separate method in CE allows EE to more easily extend it.
|
| | |
| |
| |
| |
| |
| |
| | |
EE has some custom behaviour that needs to run before and after creating
a group in the API. By moving the group creation logic to a separate
method, EE can easily extend this behaviour; without having to directly
modify the API source code.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This replaces API::Notes::NOTEABLE_TYPES and
API::Discussions::NOTEABLE_TYPES with class methods defined in a
separate helper modules. This allows EE to extend the list of noteable
types, without having to modify the constant in-place. We can't define
these methods directly in the API classes, as they would be used before
we're able to extend them in EE.
|
| | |
| |
| |
| |
| |
| | |
The repository_path is no longer needed since
https://gitlab.com/gitlab-org/gitlab-shell/merge_requests/231, which closes
https://gitlab.com/gitlab-org/gitlab-shell/issues/135.
|
| | |
| |
| |
| |
| | |
Instead of mixing in the shared secret into the querystring or body,
we could also specify it in a header.
|
| | |
| |
| |
| |
| | |
Adds custom validator for ArrayNoneAny param
Extracts some logic in js into separate files
|
| | |
| |
| |
| | |
This reverts merge request !24982
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Significantly reduce N+1 queries in /api/v4/todos endpoint
Closes #40378
See merge request gitlab-org/gitlab-ce!25711
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
By preloading associations and batching issuable metadata lookups,
we can significantly cut the number of SQL queries needed to load
the Todos API endpoint.
On GitLab.com, my own tests showed my user's SQL queries went
from 365 to under 60 SQL queries.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40378
|
| | | |
| | |
| | |
| | |
| | | |
Adds custom validator for ArrayNoneAny param
Extracts some logic in js into separate files
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow all snippets to be accessed by API
Closes #41888
See merge request gitlab-org/gitlab-ce!25772
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, you could only access personal snippets in the API if you
had authored them. The documentation doesn't state that this is the
case, and it's quite surprising.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This style change enforces `return if ...` instead of
`return nil if ...` to save maintainers a few minor review points
|