API: Add Topics API
What does this MR do and why?
In the UI, there have been some recent enhancements for project topics:
- Thanks to !71033 (merged), an admin can manage topics.
- Thanks to !62443 (merged), a user can explore topics.
Let's reflect these UI enhancements on the API as well: This MR adds a new Topics API with the following endpoints:
- Get topics
- Get topic
- Create topic (admin only)
- Update topic (admin only)
How to set up and validate locally
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
closes #345788 (closed)
Merge request reports
Activity
- Resolved by Marcin Sedlak-Jakubowski
Hi
@gl-docsteam
, please review this documentation Merge Request.Please also consider updating the
CODEOWNERS
file in the https://gitlab.com/gitlab-org/gitlab project.Edited by Amy Qualls
added documentation twtriaged labels
👋 @wwwjonThank you for your contribution to GitLab. We believe that everyone can contribute and contributions like yours are what make GitLab great!
- Our Merge Request Coaches will ensure your contribution is reviewed in a timely manner*.
- If you haven't, please set up a
DANGER_GITLAB_API_TOKEN
. - You can comment
@gitlab-bot label ~"group::"
to add a group label. - After a few days, feel free to ask
@gitlab-bot help
or ping a Merge Request Coach. - Read more on how to get help.
This message was generated automatically. You're welcome to improve it.
added Community contribution label
- Resolved by Heinrich Lee Yu
@gitlab-bot label ~"group::workspace"
requested review from @msedlakjakubowski and @fneill
@msedlakjakubowski I'll pick this one up since I'm TW for ~"group::workspace"
Edit: Just saw Amy's message re both groups, NM!
Edited by Fiona Neillassigned to @wwwjon
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
changed milestone to %14.5
added Technical Writing backend docsfeature tw-weight5 twdoing typefeature labels and removed twtriaged label
removed review request for @msedlakjakubowski and @fneill
added sectiondev label
@msedlakjakubowski Thanks for your review! I applied your suggestions. So back to you
🏓 requested review from @msedlakjakubowski
requested review from @m_frankiewicz
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
@wwwjon Docs look great!
added twfinished label and removed twdoing label
removed review request for @msedlakjakubowski
- Resolved by Heinrich Lee Yu
👋 @msedlakjakubowski
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, please start a new pipeline before merging.
For more info, please refer to the following links:
1 Warning ⚠ This merge request is quite big (536 lines changed), please consider splitting it into multiple merge requests. 1 Message 📖 This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
doc/api/api_resources.md
doc/api/topics.md
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Zamir Martins Filho ( @zmartins
) (UTC-5)Robert Speicher ( @rspeicher
) (UTC-6)workhorse Ash McKenzie ( @ashmckenzie
) (UTC+11)Alessio Caiazza ( @nolith
) (UTC+1)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
🚫 Dangermentioned in issue #340920 (closed)
- Resolved by Heinrich Lee Yu
- Resolved by Heinrich Lee Yu
- Resolved by Alessio Caiazza
- Resolved by Alessio Caiazza
- Resolved by Alessio Caiazza
- Resolved by Alessio Caiazza
- Resolved by Heinrich Lee Yu