GitLab Next

The previous URL had two drawbacks:

1. It didn't match what the title was about (`Assignments to DevOps
   Stages and Groups`, and the anchor was `#designated-technical-writers`).
2. It didn't account for the other sections, like development and API
   guidelines.

- Having the name of the feature be "JUnit test reports" can cause
  confusion over what type of support this feature has. While it
requires the JUnit format, many different languages support that format.
For a non-GitLab user this could lead away from investigating a feature
that might work well for them, just because their primary use case does
not involve Java.

MR widget that shows the new and resolved issues is now in GitLab Core
Code Quality report tab in pipeline remains in GitLab Starter and above

Fixes one version text line, and adds missing
stage metadata to related files in the same dir

* See #118824
* Extract the Testing and reports in merge requests
  section of the Merge requests doc page was moved to its own document
  to make the index easier to go through.

Links to issues need to be update to use a hyphen,
this MR changes issue links in /doc/user

Related to #205174

- Also mention epics
- Add the number of characters (1 million)
- Mention that this limit might be changed in the future

The pipelines docs are under `user/project` but should be
with the rest of the CI docs under `/ci`

This change updates the location of `settings.md` and the
`pipelines.md`

* move `/user/project/settings.md` to `ci/pipelines` folder

* update references to `settings.md` to point to the new location

* move images to the new location and delete the old directory

* move `pipelines.md` to `index.md` in the new ci/pipelines folder

Moving compliance docs into new Compliance section

The pages included in this commit all had missing Oxford (serial)
commas. In most cases, I added the comma but took no other action;
a few pages required slight rewording.

Apply suggestions to accessibility_testing.md

- Create a new document for introduction to MRs
- Document all the ways to create a MR
- Move content accordingly

This moves the description of the merge request
into a 'Overview' tab. The overview tab will now hold
the merge request widget, description and discussions.

#33813

Fix old content and improve structure, and remove
repetition. Also brings back content deleted by accident

Move several features from create MR doc to
review MR doc. Also splits security reports into
it's own section, to allow for one ULTIMATE badge

Fix links to moved content, and add front matter
to new files.

Continued work on creating_merge_requests.md
by adding section for important basic details
on the workflow, and adding/removing links
and sections as necessary. Drastically simplifies
documentation for MRs.

Update links in various pages to updated locations

Remove all duplicated information, consolidate it all in
tables, and update links. First pass.

Split docs into an index, a create MR doc, and a review MR
doc. [ci skip]

Moved MR doc features around, and updated links
to those sections

Alternate method of listing MR features

Moves the final 5 docs out of /workflow and
into their correct locations. Updates links
both inside the docs, and TO the docs, and
ensures all moved docs are linked from a
the appropriate index. Disqus comments moved too.

Feature branches should be deleted after being merged into a stable
branch like master. This is not universally true, and accidentally
deleting a branch cause frustration and confusion for users.

The change:
- adds a Project Setting to control if 'Delete source branch' option is
enabled or disabled for new merge requests
- the Project Setting is on for new and existing projects

The previous default behaviour can be restored by toggling the new
setting.

Historically, the behaviour was changed to delete the source branch as
part of the merge widget refactor and then reverted 3 months later.

- Widget refactor 8db76243
- Behaviour reverted fd72b4ed

Fix all links to blog posts to use the new
path of about.gitlab.com/blog

Centralize all git push options docs under /user/project
and format in a standardized way to allow for easier
updating and expansion

Update redirected and 404 links in import, integration
and various Plan docs.

Now a intra-project MR can be specify as
a blocking MR