Commit d3d494bc authored by Katrin Leinweber's avatar Katrin Leinweber Committed by Marcel Amirault

Clarify meaning of Git ref in CI artifacts context

parent 08344e29
...@@ -89,8 +89,9 @@ artifacts, as described in the [troubleshooting documentation](../../../administ ...@@ -89,8 +89,9 @@ artifacts, as described in the [troubleshooting documentation](../../../administ
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50889) in GitLab Core 13.9. > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50889) in GitLab Core 13.9.
When enabled (default), the artifacts for the most recent pipeline for a ref are When enabled (default), the artifacts of the most recent pipeline for each Git ref
locked against deletion and kept regardless of the expiry time. ([branches and tags](https://git-scm.com/book/en/v2/Git-Internals-Git-References))
are locked against deletion and kept regardless of the expiry time.
When disabled, the latest artifacts for any **new** successful or fixed pipelines When disabled, the latest artifacts for any **new** successful or fixed pipelines
are allowed to expire. are allowed to expire.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment