Get a list of visible projects for authenticated user in Gitlab
A documented Gitlab operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get a list of visible projects for authenticated user
- GETReads data · projects
gitlab.com/v3/projects/visible
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Gitlab operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Gitlab operations
- Add new email address to the currently authenticated userPOST · changes data
- Create a user. Available only for adminsPOST · changes data
- Add an email address to a specified userPOST · changes data
- Create a new project issuePOST · changes data
- Add a new SSH key to the currently authenticated userPOST · changes data
- Create new file in repositoryPOST · changes data
- Delete an email address of a specified userDELETE · changes data
- Create a new system hookPOST · changes data
Questions
- Can HumDay get a list of visible projects for authenticated user in Gitlab?
- Yes. This operation is published in Gitlab's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Gitlab account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Gitlab.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Gitlab account.
Where this came from
Read from a published API description for Gitlab at axil.gitlab.io/swaggerapi/static/swagger.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.