Create a label in Gitea .
A documented Gitea . operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Create a label
- POSTChanges data · issue
/repos/{owner}/{repo}/labels
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. Because this one changes data, it cannot run until you have explicitly granted it.
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 create a label 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.
- Will this change my Gitea . data?
- Yes — this is a POST operation, so it changes something in Gitea .. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- 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.