Get the authenticated user in Gitea .
A documented Gitea . 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 the authenticated user
- GETReads data · user
/user
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 Gitea . 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 Gitea . operations
- Add email addressesPOST · changes data
- Delete email addressesDELETE · changes data
- Creates a new OAuth2 applicationPOST · changes data
- Create an access tokenPOST · changes data
- Create a public keyPOST · changes data
- Create a repositoryPOST · changes data
- Create a GPG keyPOST · changes data
- Create an issue. If using deadline only the date will be taken intoPOST · changes data
Questions
- Can HumDay get the authenticated user in Gitea .?
- Yes. This operation is published in Gitea .'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 Gitea . account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Gitea ..
- 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 Gitea . account.
Where this came from
Read from a published API description for Gitea . at try.gitea.io/swagger.v1.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.