Rename license management artifact
What does this MR do?
This MR renames the License Management artifact file from the too broad gl-license-report.json
to
gl-license-management-report.json
It also adds back License Management docs that were removed from 10.8 due to non shipped feature. These changes apply mainly to these docs ; License Management is to be shipped in 11.0
Are there points in the code the reviewer needs to double check?
None, it's all documentation and a constant change in code.
Why was this MR needed?
To use an artifact name that's more precise.
Does this MR meet the acceptance criteria?
[ ] Changelog entry added, if necessary-
Documentation created/updated [ ] API support added[ ] Tests added for this feature/bug- Conform by the code review guidelines
[ ] Has been reviewed by a UX Designer[ ] Has been reviewed by a Frontend maintainer-
Has been reviewed by a Backend maintainer [ ] Has been reviewed by a Database specialist
-
EE specific content should be in the top level /ee
folder -
Conform by the merge request performance guides -
Conform by the style guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them [ ] Internationalization required/considered[ ] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan-
End-to-end tests pass ( package-qa
manual pipeline job)
What are the relevant issue numbers?
Closes #6171 (closed)
Edited by Philippe Lafoucrière