HeyBobFrom a request to a pull request.
Connect GitHub and Bob searches the code, reads the changes, files the issue and opens the pull request, asking before anything changes. In the HeyBob app on Mac, Windows and Linux, or in Slack.
- Your own GitHub access
- Asks before every change
- A receipt on every job
What Bob can do in GitHub.
He uses the access of the person who connected it. Questions about the code no longer need an engineer to relay them.
Search and read
Search code, read files, and list issues and pull requests, including what a pull request changes.
File and comment
Open an issue with the details from the conversation, or add a comment.
Make the change
Create a branch, commit the files and open a pull request for normal review.
Five things to hand him.
Start with a question about the code. Move to a small change once the answers are right.
“Find the code that decides whether an invoice is overdue. Explain how it works and name the files.”
An answer grounded in the code, with the files to check.
“Read PR 842, the linked Linear issue and the incident note. Sum up what changes for users and what could break.”
GitHub has the change. The other tools have the reason for it.
“Open a GitHub issue for this bug with the error, the expected result and what done looks like, from this thread.”
He shows you the issue before he files it.
“Add the new setting to the setup guide, run the checks that apply, and open a pull request.”
Your repository rules and checks still decide whether it goes in.
“Every Friday, sum up merged work, pull requests open too long and release risks. Join GitHub with Linear, but do not rank people.”
A brief about the work, not a leaderboard.
Connected in a minute.
Tell Bob to connect GitHub.
Tap the button he posts and sign in to the GitHub account he should use.
Review which organizations and repositories you are letting him reach.
Come back and ask again. The job picks up from there.
Each person connects their own GitHub. Bob works with that person’s repositories and permissions, including any limits your organization sets.
He opens the pull request. People merge it.
- No way around permissions. He cannot read or change a repository the connected person cannot.
- No merging here. His GitHub actions stop at opening the pull request.
- Your rules still apply. Protected branches, required reviews, tests and code owners stay in charge.
- Every change asks. Issues, comments, branches, commits and pull requests wait for your OK, and the receipt shows who approved.
Common questions.
What can Bob do with GitHub?
Search and read code, issues and pull requests, open issues and comments, create branches, commit files and open pull requests.
Whose GitHub access does Bob use?
The person who connected GitHub. Each person connects their own account.
Does Bob ask before changing a repository?
Yes. Every change asks first unless you have allowed that exact kind of change.
Can Bob merge a pull request?
Not through this connection. He opens the pull request, and your team reviews and merges it the usual way.
Hand Bob the small change nobody gets to.
$100 of work, on us. Set up in 2 minutes.