Remove outdated packages workflow doc
What does this MR do?
This workflow https://docs.gitlab.com/ee/user/packages/workflows/monorepo.html was added because previously the npm endpoint did not support all of the relevant npm commands. As a workaround, we asked users to use the publishConfig field in their package.json to define where a given package should be published to. This section of the docs primarily walks through that use case. Now that #220985 (closed) is complete, we should remove this outdated workflow.
In addition, the other sections are duplicative of other content in the docs.
Screenshots (strongly suggested)
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