An error occurred fetching the project authors.
- 18 Jan, 2022 1 commit
-
-
Coung Ngo authored
Update sort name on list views such as issues, merge requests, and epics https://gitlab.com/gitlab-org/gitlab/-/issues/23775 Changelog: changed
-
- 12 Jan, 2022 1 commit
-
-
Serhii Yarynovskyi authored
The delete_branch_confirmation_modals feature flag is removed per: https://gitlab.com/gitlab-org/gitlab/-/issues/329052 Since it was introduced to 100% of actors Changelog: removed
-
- 11 Nov, 2021 1 commit
-
-
Lukas 'Eipi' Eipert authored
This overwrites `Rails.confirm` from `@rails/ujs` in order to show a modal instead of a Browser `window.confirm`.
-
- 29 Jul, 2021 1 commit
-
-
Yorick Peterse authored
These methods were scoped to a connection in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65262. A discussion after the merge request was merged revealed these methods aren't tied to a specific connection, and as such better belong in Gitlab::Database. I briefly considered moving them to the Gitlab module instead, as the methods don't actually run any database queries. Unfortunately, this isn't possible as this module is loaded too early to prepend it with an EE module.
-
- 27 Jul, 2021 1 commit
-
-
Yorick Peterse authored
This module contained various methods that were forwarded to Gitlab::Database::Connection. This commit removes these wrappers in favour of using Gitlab::Database.main instead. This is done to make it explicit what database connection should be used. See https://gitlab.com/gitlab-org/gitlab/-/issues/331776 and https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65262 for more information.
-
- 28 May, 2021 1 commit
-
-
Jackie Fraser authored
Replaces the bootstrap modal for the delete branch button and confirmation. Changelog: added
-
- 25 May, 2021 1 commit
-
-
Jeremy Elder authored
Update button variant and alignment in the Projects::BranchesController#index and update tests to follow current guides. Changelog: added
-
- 14 Apr, 2021 1 commit
-
-
Jose Vargas authored
This removes the aforementioned feature flag, enabling the migrated dropdown component across all instances of GitLab
-
- 06 Apr, 2021 1 commit
-
-
Jose Ivan Vargas authored
-
- 10 Feb, 2021 1 commit
-
-
Patrick Steinhardt authored
With the preceding commit, the project tests which verify listing of active and stale branches works as expected start to fail. This is not a bug in the preceding commit, but rather a bug in the tests themselves: while we were using `travel_to()` to create stale branches, they were created via Gitaly's `UserCommitFiles()` RPE. This RPC doesn't accept any timestamp and thus the resulting commits do not carry the timestamp set by `travel_to()`. With the preceding commit, this now gets handled correctly such that the commits do carry the expected timestamp, which uncovers two issues: 1. There is a race between creation of active branches and checking for stale branches. The oldest active branch is only a second younger than the stale-branch threshold. Thus, if we need longer than that second, it will be considered stale, too. 2. We do expect stale branches to be sorted in descending recency order, but in fact they're ordered in ascending recency: the oldest branch is on top. Fix the tests by incrementing branch creation times by an hour instead of by a second, which extends the race window for the oldest active branch to one hour. And second, by correctly sorting expected branches.
-
- 09 Oct, 2020 1 commit
-
-
samdbeckham authored
Ran another find + Replace on the specs
-
- 02 Oct, 2020 1 commit
-
-
Alishan Ladhani authored
- In cases where `Timecop.freeze` is called with a specific time - Only in spec directory
-
- 20 Aug, 2020 1 commit
-
-
Kyle Wiebers authored
-
- 16 Jun, 2020 1 commit
-
-
Arturo Herrero authored
The plan for RSpec 4.0 is to disable monkey patching: https://rspec.info/blog/2013/07/the-plan-for-rspec-3/#zero-monkey-patching-mode This commit stops using RSpec monkey patching in some specs: https://relishapp.com/rspec/rspec-core/docs/configuration/zero-monkey-patching-mode
-
- 14 Jun, 2020 1 commit
-
-
Lee Tickett authored
-
- 09 Oct, 2019 2 commits
-
-
Jesse Hall authored
-
Jesse Hall authored
-
- 02 Oct, 2019 1 commit
-
-
Douglas Barbosa Alexandre authored
Whitelist route to compare Git revisions
-
- 26 Jul, 2019 1 commit
-
-
Thong Kuah authored
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
-
- 25 Apr, 2019 1 commit
-
-
Oswaldo Ferreira authored
We have the spec files containing EE specific code for spec/features/protected_branches_spec.rb and spec/features/protected_tags_spec.rb. This commit extracts the EE behavior into ee/ folder.
-
- 20 Feb, 2019 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 11 Jul, 2018 2 commits
- 12 Apr, 2018 2 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
- 11 Apr, 2018 2 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
- 06 Mar, 2018 1 commit
-
-
Takuya Noguchi authored
-
- 22 Dec, 2017 2 commits
-
-
blackst0ne authored
-
Vitaliy @blackst0ne Klachkov authored
-
- 02 Nov, 2017 1 commit
-
-
Mike Greiling authored
-
- 07 Oct, 2017 1 commit
-
-
Jacopo authored
Replaces all the explicit include metadata syntax in the specs (tag: true) into the implicit one (:tag). Added a cop to prevent future errors and handle autocorrection.
-
- 29 Sep, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 25 Sep, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 17 Aug, 2017 1 commit
-
-
kushalpandya authored
-
- 13 Aug, 2017 1 commit
-
-
Stan Hu authored
This needs two patches in Capybara: * https://github.com/teamcapybara/capybara/pull/1902 * https://github.com/teamcapybara/capybara/pull/1903
-
- 28 Jul, 2017 2 commits
-
-
-
Lin Jen-Shin authored
-
- 27 Jul, 2017 2 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-