| Age | Commit message (Collapse) | Author |
|---|
|
Make archived projects completely read-only
Closes #44788
See merge request gitlab-org/gitlab-ce!18136
|
|
'backport-of-rd-3429-enabling-maximum-file-size-limit-in-repository-causes-pushes-to-fail' into 'master'
Backport of EE !4989
See merge request gitlab-org/gitlab-ce!18238
|
|
Optimise rendering of Markdown documents that belong to different projects
See merge request gitlab-org/gitlab-ce!18157
|
|
Fix empty state for build that does not have a trace
Closes #45204
See merge request gitlab-org/gitlab-ce!18278
|
|
|
|
Fix finding wiki file when Gitaly is enabled
Closes gitaly#1126
See merge request gitlab-org/gitlab-ce!18317
|
|
Fixes gitaly#1126
|
|
Client implementation for InfoAttributes
See merge request gitlab-org/gitlab-ce!18261
|
|
Resolve "Illustration for the case where the job has finished and the log was erased"
Closes #45159
See merge request gitlab-org/gitlab-ce!18253
|
|
Clients can now request the attributes from `$GIT_DIR/info/attributes`
through Gitaly. The Gitaly migration is described in gitlab-org/gitaly#1082.
The parser algorithm was implemented in a way it could handle both file
contents or a File handle, and both were already tested.
Other than that, using the boy scout rule, I've removed a class,
InfoAttributes, as it was delegating everything to the parser and
therefor wasn't really needed in my opinion.
|
|
This refactors the Markdown pipeline so it supports the rendering of
multiple documents that may belong to different projects. An example of
where this happens is when displaying the event feed of a group. In this
case we retrieve events for all projects in the group. Previously we
would group events per project and render these chunks separately, but
this would result in many SQL queries being executed. By extending the
Markdown pipeline to support this out of the box we can drastically
reduce the number of SQL queries.
To achieve this we introduce a new object to the pipeline:
Banzai::RenderContext. This object simply wraps two other objects: an
optional Project instance, and an optional User instance. On its own
this wouldn't be very helpful, but a RenderContext can also be used to
associate HTML documents with specific Project instances. This work is
done in Banzai::ObjectRenderer and allows us to reuse as many queries
(and results) as possible.
|
|
into 'master'
Resolve "Clean outdated flaky specs from the flaky specs report"
Closes #37721
See merge request gitlab-org/gitlab-ce!18196
|
|
Branch with a commit detection defaults to Gitaly
See merge request gitlab-org/gitlab-ce!18304
|
|
Tag with a commit detection defaults to Gitaly
See merge request gitlab-org/gitlab-ce!18305
|
|
|
|
|
|
|
|
It also adds a fallback that covers other edge cases that might surface
later.
|
|
This could only be possible for users that can create merge requests
within a project.
So they need to be a allowed to create a branch and create a merge request.
|
|
|
|
By default this was an OPT_IN RPC, and now graduates to OPT_OUT as the
acceptance testing was successful in:
gitaly#1009
This follows the conventions of our [migration
process](https://gitlab.com/gitlab-org/gitaly/blob/master/doc/MIGRATION_PROCESS.md)
|
|
By default this was an OPT_IN RPC, and now graduates to OPT_OUT as the
acceptance testing was successful in:
https://gitlab.com/gitlab-org/gitaly/issues/1008
This follows the conventions of our [migration
process](https://gitlab.com/gitlab-org/gitaly/blob/master/doc/MIGRATION_PROCESS.md)
|
|
prevent confusion with destroy_protected_branch
|
|
RspecFlaky::Report class
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Expose the target commit ID through the tag API
See merge request gitlab-org/gitlab-ce!18248
|
|
|
|
|
|
Move FindLicense RPC to OPT OUT status
See merge request gitlab-org/gitlab-ce!18228
|
|
This is useful for annotated tags, where the deferenced target is not the same as the tag object. At the moment there is no way to differentiate the two through the tag API.
This change adds a "target" property and leaves the existing "commit" property alone so that existing behaviour is not altered.
|
|
|
|
|
|
The TIMESTAMP data type is used for values that contain both date and
time parts. TIMESTAMP has a range of '1970-01-01 00:00:01' UTC to
'2038-01-19 03:14:07' UTC.
A Forever lib class was included to handle future dates for PostgreSQL
and MySQL, also changes were made to DeployToken to enforce Forever.date
Also removes extra conditional from JwtController
|
|
Also, fixes broken specs
|
|
|
|
Also:
- Changes scopes from serializer to use boolean columns
- Fixes broken specs
|
|
|
|
- Remove extra method for authorize_admin_project
- Ensure project presence
- Rename 'read_repo' to 'read_repository' to be more verbose
|
|
- When using 'read_repo' password and project are sent, so we used both
of them to fetch for the token
- When using 'read_registry' only the password is sent, so we only use
that for fetching the token
|
|
This will allow to download a repo using the token from the DeployToken
|
|
Resolve "Wrong empty state for cancelled build, hides existing logs!"
Closes #42568
See merge request gitlab-org/gitlab-ce!17646
|
|
Repository checksum calculation is handled by Gitaly when feature is enabled
See merge request gitlab-org/gitlab-ce!18210
|
|
Add support for patch link extension for commit links on GFM
Closes #17939
See merge request gitlab-org/gitlab-ce!18229
|
|
Fix 500 error when MR from fork has conflicts but worker has not run
See merge request gitlab-org/gitlab-ce!18226
|
|
|
|
|
|
|
|
|
|
Automatically cleanup stale worktrees and lock files upon a push
Closes #44115
See merge request gitlab-org/gitlab-ce!18095
|
|
|
