| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Remove readme project_view option
See merge request !11425
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Render plain README using Markup viewer so it is displayed below tree
See merge request !11510
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Stop MR conflict code from blowing up when branches are missing
Closes #32544
See merge request !11501
|
| | | |
|
| |\ \
| |/
|/|
| | |
See merge request !11346.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix root groups redirecting to group owner
Closes #32474
See merge request !11465
|
| | | | |
|
| | |/
| |
| |
| | |
Older namespace records may be both `type == ‘Group` AND `owner_id` is not null.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Incorporate Gitaly's local_branches operation into repo code
Closes #27379
See merge request !10059
|
| | | | |
|
| | |/
|/| |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Invalidate cache for issue and MR counters separately
See merge request !11394
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Move some blob viewer stuff around without changing behavior
See merge request !11358
|
| | | | |
| | | |
| | | |
| | | | |
max_size
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Foreign key for Pipeline schedule owner
Closes #31932
See merge request !11233
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the owner of a pipelines schedule was either blocked or was removed
from the project, the pipeline schedular would still schedule the
pipeline.
This would than fail however, given the user had no access to the
project and it contents. However, a better way to handle it would be to
not schedule it at all. Furthermore, from now on, such schedules will be
deactivated so the schedule worker can ignore it on the next runs.
|
| | | |
| | |
| | | |
This reverts merge request !11287
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Rename all references to rendered_title to realtime_changes
See merge request !11359
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
| | | |/
| |/| |
|
| |/ /
| |
| |
| |
| |
| | |
It seems that bad things happen when two gRPC stubs share one gRPC
channel so let's stop doing that. The downside of this is that we
create more gRPC connections; one per stub.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Fetch commit deltas from Gitaly
Closes gitaly#199
See merge request !11122
|
| | |
| |
| |
| | |
Closes gitaly#199
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix conflict resolution from corrupted upstream
Closes gitlab-ee#2128
See merge request !11298
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I don't know why this happens exactly, but given an upstream and fork repository
from a customer, both of which required GC, resolving conflicts would corrupt
the fork so badly that it couldn't be cloned.
This isn't a perfect fix for that case, because the MR may still need to be
merged manually, but it does ensure that the repository is at least usable.
My best guess is that when we generate the index for the conflict
resolution (which we previously did in the target project), we obtain a
reference to an OID that doesn't exist in the source, even though we already
fetch the refs from the target into the source.
Explicitly setting the source project as the place to get the merge index from
seems to prevent repository corruption in this way.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Usage ping updates
Closes #31741 and #31453
See merge request !11231
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Setting `usage_ping_enabled` to false in `gitlab.yml`:
1. Disables the usage ping, regardless of the value stored in the database.
2. Prevents the usage ping from being enabled through the admin panel. It can
only be enabled by either removing the line from `gitlab.yml` and configuring
through the admin panel, or setting it to true in `gitlab.yml`.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Improve project list cache key
Closes #31863
See merge request !11325
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Expose memory deltas between app deployments and refactor prometheus queries to support more custom queries
See merge request !10981
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
+ fix tests
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Tests for prometheus queries
- fix rubocop warnings
- Remove unused method. Add more queries to deployment queries.
- Wrap BaseQuery in module hierarchy
Renname Prometheus class to PrometheusClient
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Rework update_assignee_cache_counts
Closes #31873
See merge request !11270
|
| | | |_|_|/ /
| |/| | | | |
|
| |\ \ \ \ \ \
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Enabled 'no one' as a merge access level in protected branches
Closes #31541
See merge request !11232
|
| | | | | | | |
|
