What authentication does the Gogs API use?

Gogs supports two schemes: HTTP basic authentication with username and password, and personal access tokens passed via the Authorization header. Through Jentic, both are stored encrypted in the vault and injected at execution time so the agent never sees the raw secret.

Can I create an issue with the Gogs API?

Yes. POST /repos/{owner}/{repo}/issues opens a new issue and POST /repos/{owner}/{repo}/issues/{index}/comments adds a comment. The shape mirrors the GitHub Issues API so existing tooling ports across with little change.

What are the rate limits for the Gogs API?

Gogs is self-hosted and the OpenAPI spec does not declare a numeric rate limit. The practical limit depends on the deployed server's capacity; back off on HTTP 429 responses if your administrator has fronted the server with a rate-limiting proxy.

How do I migrate a repository to Gogs through Jentic?

Run a Jentic search for 'migrate repo to gogs', load the schema for POST /repos/migrate, and execute it with the source clone URL and target organisation. Install with pip install jentic and chain search, load, and execute.

Does the Gogs API support webhooks?

Yes. /repos/{owner}/{repo}/hooks lists configured webhooks and POST to the same path adds a new one. /repos/{owner}/{repo}/hooks/{id} updates or removes a specific webhook so CI integrations can keep their delivery URLs current.

Can I limit what my agent is allowed to do with the Gogs API?

Yes. Because Jentic One is self-hosted by you, your own rules decide which Gogs operations and credentials the agent may use. Gogs puts the owner and repository in the URL path, such as /repos/{owner}/{repo}/issues, so you can pin the agent to a single repository where it reads and files issues, lists branches, and reads releases and nothing more. Sensitive operations like POST /repos/migrate are excluded unless you explicitly add them, and your Gogs token or basic-auth credential is injected at execution time rather than exposed to the agent.