Review queue
The engineering lead asks what is waiting for review. Memtro lists five open pull requests across three repositories, with requested reviewers, and points out that the oldest, from Dan Fletcher, has waited nine days.
Gitea + Memtro
Ask Gitea which pull requests are waiting for review and what changed this week.
Connect Gitea with an access token and Memtro searches repositories, issues and pull requests with their comments, labels and reviewers, lists commits, and reads Actions runs. Leave the host blank for gitea.com, or type your own server. The token acts as its user within the scopes you tick. When you ask, and once an administrator has granted them by name, it can open, edit and close issues and pull requests, comment, label, assign, review and merge, create branches and releases, and run, re-run or cancel Actions workflows, which may deploy. Deleting an issue or comment is permanent.
In Memtro
What you can do with Gitea in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Gitea tool, reads what it needs, and answers with the source cited.
What it does
- 01Repositories by name with visibility, default branch and open issue and pull request counts
- 02Issues and pull requests across repositories by state, labels, words and updated date
- 03One issue or pull request with its body and recent comments, and pull requests with reviewers
- 04Commits by branch, path or date, and Actions runs with status and conclusion
- 05When asked and granted, opens, edits, closes, locks or permanently deletes issues, comments, assigns people, and creates or changes labels and milestones
- 06When asked and granted, opens, updates, reviews and merges pull requests, creates branches and releases, and runs, re-runs or cancels Actions workflows, which can build and deploy
Acts when asked
When you ask it to
These tools change something in Gitea. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Open an issue in a repository
- 02Comment on an issue or pull request
- 03Add existing labels to an issue or pull request
- 04Change an issue's title, replace its body, or close or reopen it
- 05Remove a label from an issue or pull request
- 06Delete a comment permanently
- 07Replace the full set of labels on an issue or pull request
- 08Delete an issue permanently
- 09Merge a pull request into its base branch
- 10Submit a pull request review (approve, request changes or comment)
- 11Create a release and its tag (a draft unless asked to publish)
- 12Open a pull request from one branch into another
- 13Change a pull request's title, body, base branch or due date, or close or reopen it
- 14Bring a pull request's branch up to date with its base (merge or rebase)
- 15Request reviews on a pull request
- 16Assign people to an issue or pull request
- 17Replace the text of a comment
- 18Lock an issue or pull request conversation
- 19Create a label in a repository
- 20Create a milestone in a repository
- 21Create a branch
- 22Edit a release or publish a draft release
- 23Run an Actions workflow on a branch or tag
- 24Re-run an Actions workflow run
- 25Re-run the failed jobs of an Actions workflow run
- 26Cancel an Actions workflow run
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Gitea for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Gitea signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01Commits pushed
- 02A branch or tag was created
- 03A branch or tag was deleted
- 04The repository was forked
- 05A release was published, updated or deleted
- 06A repository was created or deleted
- 07A package was published or deleted
- 08A commit status changed
- 09An issue was opened, edited, closed or reopened
- 10An issue was assigned or unassigned
- 11An issue's labels changed
- 12An issue's milestone changed
- 13Someone commented on an issue
- 14A pull request was opened, edited, closed, merged or reopened
- 15A pull request was assigned or unassigned
- 16A pull request's labels changed
- 17A pull request's milestone changed
- 18Someone commented on a pull request
- 19A pull request was approved
- 20Changes were requested on a pull request
- 21A pull request review left comments
- 22New commits were pushed to a pull request
- 23A review was requested on a pull request
- 24An Actions workflow run changed
- 25An Actions job changed
In practice
Ask it like you would a colleague
Once Gitea is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Gitea + Memtro
Which pull requests are waiting for review?
What was merged into main this week?
Did the last Actions run on the api repository pass?
Open an issue about the broken Acme login page
Re-run the failed jobs on the last api build
Merging and releasing
Priya Sharma asks Memtro to squash-merge the approved Northwind fix and create release v2.4.0. With both actions granted, Memtro merges the pull request into main and creates the release as a draft, seen only by people with write access and notifying nobody, until she publishes it in Gitea.
Teams
Where it fits
The teams that lean on Gitea most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in Gitea is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Work managementGitea with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementGitea with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementGitea with LinearIssues, projects and teams, synced hourly into memory.
- SupportGitea with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportGitea with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportGitea with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisGitea with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisGitea with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisGitea with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withAccess token
- 1
In Gitea open your avatar → Settings → Applications → Manage Access Tokens and name it Memtro. Consider a dedicated user with access to just the repositories Memtro should see
- 2
Under Select permissions set repository, issue and user to Read. Set issue to Read and Write if Memtro may change issues, comments and labels, and repository to Read and Write if it may merge or review pull requests, create releases or run workflows
- 3
Paste the Access token, shown once, into Connections → Gitea in Memtro. Leave Host blank for gitea.com, or type your server's host name only, with a publicly trusted certificate. Actions runs need Gitea 1.24 or later
- 4
Ask which pull requests are waiting for review
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Gitea tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Gitea?+
Only when you ask, and only what it has been granted: open an issue in a repository; comment on an issue or pull request; add existing labels to an issue or pull request; change an issue's title, replace its body, or close or reopen it; remove a label from an issue or pull request; delete a comment permanently; replace the full set of labels on an issue or pull request; delete an issue permanently; merge a pull request into its base branch; submit a pull request review (approve, request changes or comment); create a release and its tag (a draft unless asked to publish); open a pull request from one branch into another; change a pull request's title, body, base branch or due date, or close or reopen it; bring a pull request's branch up to date with its base (merge or rebase); request reviews on a pull request; assign people to an issue or pull request; replace the text of a comment; lock an issue or pull request conversation; create a label in a repository; create a milestone in a repository; create a branch; edit a release or publish a draft release; run an Actions workflow on a branch or tag; re-run an Actions workflow run; re-run the failed jobs of an Actions workflow run; cancel an Actions workflow run. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a Gitea connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Gitea data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect Gitea?+
Access token. In Gitea open your avatar → Settings → Applications → Manage Access Tokens and name it Memtro. Consider a dedicated user with access to just the repositories Memtro should see.
Can Gitea start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Gitea for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Connect Gitea in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.