| Age | Commit message (Collapse) | Author |
|---|
|
backend
The previous behavior would include the Authorization header, which would
make fetching an S3 blob fail quietly.
Closes #22403
Update sh-fix-container-registry-s3-redirects.yml
|
|
Add an ability to cancel attaching file and redesign attaching files UI
Closes #15611, #24270, and #28905
See merge request !9431
|
|
when request is made
|
|
Removed the target=_blank from the monitoring component
Closes #32243
See merge request !11386
|
|
|
|
Rename `build_events` to `job_events`, take 2.
Closes #31620
See merge request !11403
|
|
|
|
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
|
Foreign key for Pipeline schedule owner
Closes #31932
See merge request !11233
|
|
'32219-speed-up-yarn-install-in-ci-by-utilizing-inter-pipeline-cache' into 'master'
Resolve "Speed up `yarn install` in CI by utilizing inter-pipeline cache"
Closes #32219
See merge request !11343
|
|
Notes warning message should go away once resolved
Closes #24373
See merge request !10823
|
|
|
|
|
|
Omega submodules
See merge request !10797
|
|
Scope recent searches to project
Closes #31902
See merge request !11142
|
|
Flash error messages disappear(`fadeOut`) automatically after any successful request
|
|
This reverts merge request !11287
|
|
Sometimes it is useful to store submodules in the same repository which
contains links to them. Make the UI support this.
See
https://github.com/twosigma/git-meta/wiki/The-Omega-Repo
for information about this strategy
Signed-off-by: David Turner <novalis@novalis.org>
|
|
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/31902
|
|
fix Resolved Discussions counter wrapping to next line
Closes #31106
See merge request !10775
|
|
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
|
|
|
Fix token interpolation when setting the Github remote
See merge request !11311
|
|
31886 Remove spinner from loading comment
Closes #31886
See merge request !11339
|
|
Allow GitLab instance to start when InfluxDB hostname cannot be resolved
Closes #24438
See merge request !11356
|
|
For backwards compatibility
|
|
Make auto-cancelling pending pipelines on by default
Closes #30656
See merge request !11023
|
|
add-index-for-auto_canceled_by_id-mysql
* upstream/master: (224 commits)
Added balsamiq jasmine integration test
Add support for deltas_only under Gitaly
Codestyle
Update CHANGELOG.md for 9.1.4
Update CHANGELOG.md for 9.1.4
Update CHANGELOG.md for 9.1.4
Update CHANGELOG.md for 9.1.4
Minor cosmetic fixes in hooks admin screen
Documentation for repository_update_events
Changelog
Update SystemHooks API to expose and handle new repository_update_events
Make the new repository_update_events configurable in System Hooks UI
Added repository_update hook
Wait for requests after each Spinach scenario instead of feature
Remove trailing comma in dependency linker to satisfy Rubocop
Fix specs
New branch new mr docs
Relax rake backup regex to handle CE and EE RCs
Fix conflict resolution from corrupted upstream
Removed all instances of Object.assign by using es6 classes, also includes some …
...
|
|
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.
|
|
Allow numeric values in gitlab-ci.yml
Closes #30017
See merge request !10607
|
|
add username field to push webhook
Closes #32136
See merge request !11272
|
|
|
|
Closes #24438
|
|
Backport New SystemHook: `repository_update`
Closes #26325
See merge request !11140
|
|
change all .nav-links to use flex
place Resolve Discussions above tabs on small screens, and to the right on large
|
|
[ci skip]
|
|
|
|
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
|
|
Improve project list cache key
Closes #31863
See merge request !11325
|
|
Autolink package names in Gemfile
See merge request !11224
|
|
|
|
# Conflicts:
# app/assets/javascripts/vue_merge_request_widget/components/mr_widget_header.js
|
|
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
|
|
'31384-new-issue-button-on-no-results-page-after-search-doesn-t-go-to-correct-form' into 'master'
Remove 'New Issue' button from 'There are no issues to show' state graphic
Closes #31384
See merge request !11263
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
Enabled 'no one' as a merge access level in protected branches
Closes #31541
See merge request !11232
|
