| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Update and fix resolvable note icons for easier recognition
Closes #36582
See merge request !13821
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Update templates to include header in the README
Closes #36904
See merge request !13785
|
| | | | |
|
| | | |
| | |
| | | |
[ci skip]
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix a transient failure in mini_pipeline_graph_spec
Closes #34323
See merge request !13844
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This spec failed reliably with a specific run order (see issue), the
reasons for which are still unknown. This simplification resolves the
failure.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/34323
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add filtered search to group merge requests dashboard
Closes #36703
See merge request !13688
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add spec for deleting protected tags
See merge request !13693
|
| | |/ / / / |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix events error importing GitLab projects
Closes #36965
See merge request !13868
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Improve flaky ACE editor spec
See merge request !13854
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The ACE editor JavaScript may not be loaded when the spec
runs evaluateScript. Wait for the editor to load before
attempting to run ACE-specific JavaScript.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
fix transient dropdown test failures
Closes #37052 and #34436
See merge request !13862
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
Instrument MergeRequest#ensure_ref_fetched
See merge request !13876
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Reenable MySQL tests on all CE and EE branches part 2
Closes #36384
See merge request !13840
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
To protect master from surprise failures, as long as we continue to support MySQL.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Don't wait for project authorization sidekiq jobs when creating projects
Closes #36792
See merge request !13775
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Only admins have the ability to create a project in another user's personal
namespace. Prior to this commit, we were explicitly adding them as masters to
the project. However, admins already have access (by virture of being admins),
so this is unnecessary.
|
| | | |_|_|_|_|_|/
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
If the project is in a group, the `group.refresh_members_authorized_projects`
is made non-blocking, and we call `current_user.refresh_authorized_projects`
directly.
Projects in a personal namespace are more difficult. Rather than passing the
`blocking:` parameter through the entire `add_master` chain, have the
`AuthorizedProjectsWorker` automatically inline authorizations for three IDs or
less. Since the maximum number of IDs in this path is 2, that has the same effect.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Combine multiple expectations into one for shared system note example
See merge request !13814
|
| | |/ / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
These are all performing unique checks on the same object, so there's no
benefit to isolating them.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
'master'
Clear schema cache after running tests for migrations
Closes #37086
See merge request !13870
|
| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Remove skipped examples in filtered issues feature spec
See merge request !13845
|
| | | |_|_|_|_|/ / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
We perform a ton of expensive setup in this spec, via both `before` and
`let!`. When we use `skip` inside an `it` block, rather than skipping
the block entirely via `xit`, we still perform this expensive setup,
only to do absolutely nothing with it, resulting in wasted time.
Minutes, in this case.
Further, these specs have been sitting in our test suite for about seven
months now, so the likelihood of them being addressed soon seems low.
|
| |\ \ \ \ \ \ \ \ \
| |_|/ / / / / / /
|/| | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Make sure we have an owner for triggers
Closes #35642
See merge request !13799
|
| | |\ \ \ \ \ \ \ \
| | | |_|_|_|/ / /
| | |/| | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
35642-add-owner-to-triggers-factory
* upstream/master: (49 commits)
Fire system hooks when a user is created via LDAP or OAuth
Common Docker Documentation Location in `gitlab-ce`
fix deprecation warning present during webpack compiles
Enable 5 lines of Sidekiq backtrace lines to aid in debugging
Add support for copying permalink to notes via more actions dropdown
Docs: update - fix headers
Handle creating a nested group on MySQL correctly
Decrease statuses batch size even more in a migration
Fix failure when issue author is nil
Fix searching for files by path
Fix invite by email address duplication
Revert "Merge branch 'mk-reenable-mysql-tests-on-all-branches' into 'master'"
Fix repo editor scrollbar
Revert "Merge branch 'sh-sidekiq-backtrace' into 'master'"
Replace 'source/search_code.feature' spinach test with an rspec analog
Add missing third argument to `Git::Repository#initialize` in spec
New doc: how to install GitLab on Azure
Authorizations regarding OAuth - style confirmation
Enable 5 lines of Sidekiq backtrace lines to aid in debugging
Reenable MySQL tests on all branches
...
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
And specify owners more clearly
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Simplify system hook testing and guarantee test will fire
Closes #37067
See merge request !13858
|
| | | |_|/ / / / / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The change in !11728 would cause an arbitrary project to be chosen to test
system hooks, and it's likely that the project would not have any commits or
relevant commits to test the hook. This would prevent admins from verifying
that the hook fired. Instead of trying to create a representative hook
dynamically, just send static data to guarantee the hook will actually be
tested.
Closes #37067
|
| |\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Bugfix.notify custom participants
Closes #36610
See merge request !13680
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | | | | | | | | | |
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
factor out #suitable_notification_level? and check manually by
notification level. this makes the notification logic clear and actually
reflect what is in the documentation as to what should happen with each
setting.
|
| | | | | | | | | | | |
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
where that custom setting is not enabled.
|
| |\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Update 'Using Docker images' documentation
Closes gitlab-ci-multi-runner#2696
See merge request !13848
|
