GitHub Integration & Workflow Automation Approvals
Run Github on autopilot. Keep the veto.
295 actions67 triggers
A branch protection rule fires or a pull request ships to review before you've read it; Rills proposes every action and waits for you to decide.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential development action from Github arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Update branch protection rule on 3 repos to require review?
Triggered by org_block event on enterprise account
Same rule applied to 2 repos last Wednesday without issues
1 repo has open PRs that would be affected immediately
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Github automation
Repository events pile up while you're heads-down: a pull request review thread closes, a branch protection rule changes, and something posts or ships before you had a chance to weigh in. The mistakes don't announce themselves; they show up as a confused teammate or a rule that nobody meant to drop.
When Github runs unsupervised
Github automation moves fast, and the actions that go out without a check are the ones you find out about after the fact.
- A branch protection rule gets updated mid-sprint and a merge goes through that should have been blocked.
- Enable auto-merge fires on a pull request before the review cycle is finished, and the code lands in main before anyone signed off.
- A pull request review comment gets posted by AI into an open thread with the wrong context, and the author spends an hour confused.
- An org_block or membership event triggers a cascade of role changes no one intended to approve.
- A discussion comment gets updated or unmarked as the answer while the author is still watching the thread.
What Rills does inside Github
When a pull request review thread closes or a milestone event fires, Rills surfaces the next logical action: add an inline comment to the PR review, update the branch protection rule, or enable auto-merge. You see the proposal before it touches anything.
The branch rule still updates; you just approve it before it ships.
When Github events should and shouldn't act on their own
Not every trigger in Github carries the same risk. Some fire on routine state changes; others touch things a human should always review first.
- watch: Low-stakes signal, safe to graduate to autonomous once the pattern is consistent.
- milestone: Routine enough for autonomous when it maps to a known project cadence with no team-facing side effects.
- project_card and project_column: Position reorders inside a ProjectV2 are low-risk and repeat often enough to learn.
- pull_request_review_thread: Closing a thread can trigger a branch action or an inline comment; always wait for your call before anything posts.
- organization: Role changes and org-level permission updates inside a development team should never ship without a named approver.
- personal_access_token_request: Security-adjacent; confidence scoring will keep this in the approval queue regardless of pattern history.
What wakes Rills up in Github
When these events fire, Rills proposes the next move and waits for your call.
Code Scanning Alert
Fires when a code scanning alert is created, fixed, or dismissed. Monitor security vulnerabilities discovered by code analysis tools.
Dependabot Alert
Fires when Dependabot detects a security vulnerability in dependencies. Monitor dependency security threats.
Deployment
Fires when a new deployment is created. Monitor production and staging deployments.
Issue Comment
Fires when a comment on an issue or pull request is created, edited, or deleted. Capture all comment activity on issues and PRs.
Issues
Fires when an issue is opened, closed, edited, or labeled. Track issue lifecycle and status changes.
Pull Request
Fires when a pull request is opened, closed, merged, or updated. Monitor the full pull request lifecycle.
What Rills can do in Github
6 of 295 actions across reads, writes, and updates.
- 01
Add labels to an issue, PR, or discussion
Attach labels to GitHub issues, pull requests, or discussions to organize and categorize your work items. This helps you triage tasks, track priorities, and keep your projects organized without manually tagging each item.
- 02
Request reviews on a pull request by user/team IDs
Automatically assign code reviewers to pull requests by specifying team or user IDs, enabling you to enforce review workflows based on code ownership or team rotation policies.
- 03
Create a new issue in a repository
Open a new issue in a GitHub repository with a title, body, labels, and assignees to track bugs, tasks, and work items. This automates issue creation from external tools and processes, helping you stay organized without manual GitHub data entry.
- 04
Update an existing issue
Modify an existing issue's title, description, status, labels, assignees, or milestone to keep your project organized and up-to-date. This helps you automate issue management tasks like triaging, reassigning, and adding context without manual updates.
- 05
Create a new pull request
Automatically create a new pull request to propose code changes from one branch to another, with customizable title, description, reviewers, and draft status.
- 06
Merge a pull request into its base branch
Automatically merge an approved pull request into your main codebase once all checks pass and reviews are complete.
Common questions about Github automation
How do I automate GitHub branch protection rule updates?
You set up a Rills workflow that watches for branch_protection_rule events and proposes the update before anything changes. Nothing applies until you approve it. Routine updates can graduate to autonomous once Rills learns your pattern, but you keep the veto the whole time.
Can I get mobile approvals before a PR merge or repo visibility change ships?
Yes. Rills queues the proposed action and waits for your call. You review it from your phone, swipe to approve or reject, and only then does it go through. A repo visibility change going out without your sign-off is exactly the situation Rills is built to prevent.
How do I automate GitHub issue and branch management without losing control?
Rills watches your chosen GitHub events, like create or delete, and proposes actions such as unlinking a branch from an issue. You decide what ships. Nothing fires automatically until you approve, so a mislinked branch or a wrong issue type does not get created behind your back.
Can Rills alert me when a Dependabot alert or code scanning alert fires?
Yes. Dependabot alerts and code scanning alerts are supported trigger events. Rills picks them up, proposes an action based on your workflow logic, and holds for your approval before anything changes in the repo. You are not finding out about a vulnerability fix that already shipped.
How do I automate GitHub enterprise org migrations safely?
Rills can propose starting an Enterprise Importer organization migration and wait for your explicit approval before the process begins. A migration that kicks off before you have reviewed the scope is a support ticket you do not want. Rills holds it until you say go.
How is Rills different from Zapier for GitHub automation?
Zapier fires actions the moment conditions are met. Rills proposes the action and waits for a human to approve before anything ships. For GitHub operations like updating branch protection rules or changing repo visibility, that pause is the point. You are not watching a Zap run something you wish you had reviewed first.
Does Rills support GitHub webhook events for triggering workflows?
Yes. Rills supports a broad set of GitHub events including check_run, check_suite, deployment_review, deployment_protection_rule, and more. When one of these fires, Rills builds the proposed action and queues it for your review rather than executing immediately.
How much does Rills cost for GitHub automation?
Approvals and workflow logic are free. You only pay for real actions, meaning the AI calls and external API work that actually execute. If a proposed GitHub action sits in your queue and you reject it, you pay nothing for that decision. The approval layer itself never costs you anything.