| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Guess the modes based on the following:
1. If the file didn't exist, it's zero.
2. If the diff contains 'Subproject commit', it might be a submodule, so 0600.
3. Otherwise, it's 0644.
This isn't perfect, but it doesn't have to be - it won't change file modes in
the repository.
|
| |\
| |
| |
| |
| |
| |
| | |
Client Implementation: RefService::RefExists
Closes gitaly#452
See merge request !13528
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Don't escape html entities in InlineDiffMarkdownMarker
Closes #36041
See merge request !13553
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Gitaly apply gitattributes
Closes gitaly#464
See merge request !13517
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
And the link to the last page cannot be `page=0`.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add specs that check the 'Link' header for the inclusion of:
- rel="first"
- rel="last"
- rel="prev"
- rel="next"
Fixes gitlab-org/gitlab-ce#36618
Related to gitlab-com/infrastructure#2532
|
| |\ \
| | |
| | |
| | |
| | | |
Backports EE mirror stuck handling feature…
See merge request !13627
|
| | | |
| | |
| | |
| | | |
(https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2628) to CE
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Improve migrations / background migrations testing strategy
Closes #36303
See merge request !13589
|
| | | |/
| |/| |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Only create commit GPG signature when necessary
See merge request !13561
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Circuitbreaker settings to avoid spec-failures
Closes #36324
See merge request !13519
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This allows testing every storage attempt after a failure. Which could
be useful for tests
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Whitelist or fix additional `Gitlab/PublicSend` cop violations
See merge request !13467
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
An upcoming update to rubocop-gitlab-security added additional
violations.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Enable Layout/TrailingWhitespace cop and auto-correct offenses
See merge request !13573
|
| | | |_|_|/
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fix CI_PROJECT_PATH_SLUG slugify
Closes #34643
See merge request !13350
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Don't depend on `Rails` for Redis configuration file paths
Closes #36514
See merge request !13575
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The `Rails` object was not always available in all tasks that require
Redis access, such as `mail_room`, so the constant pointing to the
configuration path was never defined, but we still attempted to access
it in `config_file_name`, resulting in a `NameError` exception.
Further, there was no benefit to defining these paths in a constant to
begin with -- they're only accessed in one place, and it was within the
class where they were being defined. We can just provide them at
run-time instead.
Further _still_, we were calling `File.expand_path` on the absolute path
returned by `Rails.root.join`, which was rather pointless.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Speed up project creation by inlining repository creation
Closes #34533
See merge request !13529
|
| | | |_|/
| |/| | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Remove deprecated field from workhorse API responses
See merge request !13567
|
| | | | | | |
|
| | |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Related to !13108. Mostly this is just running the rake task and
changing the task a bit to catch cases like the project already existing
or so. The rake task moves archives to the vendor/project_template
directory, which are checked in too.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Handle missing .gitmodules when getting submodule urls
See merge request !13509
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Migrate `Git::Repository.ls_files` to Gitaly
Closes gitaly#404
See merge request !13302
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix: Thread safe GPGME tmp directory
Closes #35986
See merge request !13481
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
setting of the gpg home directory is not thread safe, as the directoy
gets stored on the class.
if multiple threads change the directory at the same time, one of the
threads will be working in the wrong directory.
|
| | | | | | |
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Don't rename system when migrating from 9.x -> 9.4
Closes #35525 and #36148
See merge request !13228
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Update the markdown unconditionally since the move might have been
done before, but the markdown not updated.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Migrate force push check to Gitaly
See merge request !13406
|
| | | |_|/ /
| |/| | | |
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Enable Timecop safe mode
Closes #32004
See merge request !13498
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
Detect and keep track of flaky specs
See merge request !13021
|
| | |/ / /
| | | |
| | | |
| | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Use a separate table for storing push events
See merge request !12463
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This changes various controllers to use the new EventCollection class
for retrieving events. This class uses a JOIN LATERAL query on
PostgreSQL to retrieve queries in a more efficient way, while falling
back to a simpler / less efficient query for MySQL.
The EventCollection class also includes a limit on the number of events
to display to prevent malicious users from cycling through all events,
as doing so could put a lot of pressure on the database.
JOIN LATERAL is only supported on PostgreSQL starting with version 9.3.0
and as such this optimisation is only used when using PostgreSQL 9.3 or
newer.
|
