GitHub Issue Automation — The Way Work Starts

A GitHub issue is the most popular way to start the software-delivery team running on the Forge workflow engine . Other teams — research, content, support, operations — are started on a schedule, from another system, or by hand.

What happens when you add the label

The ticket stays the anchor for the whole run. Whatever happens, it is traceable back to the issue you labelled.

Three things route back into the run once it is going:

1. A comment on the issue — goes to the role working right now, as a follow-up question, not a restart.
2. A review comment on the pull request — threads into the reviewer’s conversation, so a review discussion is a continuation rather than a new one.
3. Changing the label — pauses, resumes, or restarts the run.

How a comment reaches the team

When you comment on an active ticket, Forge checks the message genuinely came from GitHub, finds the run attached to that issue, works out which role is currently holding the work, adds your comment to that role’s conversation, and gives it another turn. It then puts a 📥 reaction on your comment so you know it landed rather than wondering.

The same happens on pull-request review comments — those reach the reviewer.

Who the commits belong to

Forge commits, branches and pull requests are made by the Forge GitHub App, using permissions your organisation granted it — not by one person’s personal account. That matters for audit: it is obvious at a glance which changes were produced by the team and which by a colleague.

Those permissions expire after about an hour, and a single agent turn occasionally runs longer than that. Forge notices and renews mid-run, so a long piece of work does not lose everything at the final step.

What you get

Everything below is live in production today.

• A label as the entry point, with the run tied to that issue for its whole life
• Comments routed to the role currently working, on issues and on pull requests
• A saved point at every step, so you can look back or restart from one
• Commits and pull requests attributed to Forge, with permissions renewed mid-run

Try it

1. Install the Forge GitHub App on your repository.
2. Open an issue describing what you want.
3. Add the forge-pipeline label.
4. Watch the issue — each role posts a status comment when it starts.
5. Comment if you want to clarify or redirect mid-run.
6. The pull request appears in the same repository when the reviewer approves.