Add bulk delete paragraph to artifacts docs
What does this MR do?
This MR adds a paragraph describing the artifacts bulk delete feature after the paragraph about the artifacts management page feature. It also adds a warning about how deleting artifacts is a permanent operation that can delete data that certain GitLab features rely on, i.e. deleting a job's job log causes it to no longer be displayed when you navigate to that job.
Related issues
Author's checklist
-
Follow the: [ ] If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added.-
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by Miranda Fluharty