Gitea Report Issue To Existing Repository
Version 1.0.0
Confirm a repository exists, open an issue in it, and comment on it.
1 workflow
2 source APIs
1 provider
View Spec
View on GitHub
GitSource ControlDevOpsCI/CDCode HostingOpen-SourceSelf-HostedPackage RegistryIssue TrackingPull RequestsArazzoWorkflows
report-issue-to-existing-repo
Confirm a repo exists, open an issue, and comment on it.
Reads the repository to confirm it exists, opens an issue, then posts a follow-up comment on that issue.
3 steps
inputs: authToken, commentBody, issueBody, issueTitle, owner, repo
outputs: commentId, issueNumber, repoId
1
getRepo
Read the repository to confirm it exists before filing an issue.
2
openIssue
Open an issue describing the problem.
3
addDetails
Post a follow-up comment with reproduction details.
Every workflow here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for arazzo workflows
4 MCP tools reach this
find_arazzoBrowse and filter every workflow in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/gitea-report-issue-to-existing-repo-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.