Clean up stale merge request HEAD ref
What does this MR do?
14 days after a merge request gets closed/merged, its HEAD ref will be deleted and moved as a keep-around
ref (if not yet added).
This is to ensure that the commit won't be deleted when GC runs and still being able to reduce the number of advertised refs on git push/pull.
A separate MR will be opened to also delete the MR merge refs. Also, handling old MRs will be done in another release which will require a background migration.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
- [-] Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Patrick Bajao