| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This whitelists all existing offenses for the various CodeReuse cops, of
which most are triggered by the CodeReuse/ActiveRecord cop.
|
|
|
|
| |
Partially addresses #47424.
|
|
|
|
|
| |
Fixes #37438
Fixes gitaly#999
|
|
|
|
|
|
|
|
|
|
|
|
| |
In gitlab-org/gitlab-ce!13251 wildcard Protected Branches were handled
properly when deleting all merged branches. But this fix wasn't that
good. It also checked branch names against Protected Tags. That's not
correct.
This change will **only** check if there is a Protected Branch
matching the merged branch, and ignores Protected Tags.
Closes gitlab-org/gitlab-ce#39732.
|
| |
|
|
|
|
|
|
|
| |
The "Delete Merged Branches" button should filter out protected
branches matching the wildcard patterns.
Closes gitlab-org/gitlab-ce#35592.
|
|
|
|
|
| |
When deleting all the branches that are merged, the protected branches
should not be deleted.
|
|
|
|
|
|
|
|
|
| |
merged branches" service
Customers were surprised by the previous behavior, which destroyed branches
even though an open merge request existed for it.
Closes #29427
|
|
|
|
|
| |
Rails by default use autoload for all dirs from app folder.
require_relative not needed. See ActiveSupport::Dependencies.autoload_paths
|
|
It adds a button to the branches page that the user can use to delete
all the branches that are already merged. This can be used to clean up
all the branches that were forgotten to delete while merging MRs.
Fixes #21076.
|