Integrations / Source control
GitHub
Jigward works in your repositories the way a colleague does, through draft pull requests a person reviews and merges.
What Jigward can do in GitHub
-
Read code and history
A repository's code, history and metadata, read before it changes anything.
-
Search code
Across the repositories its Context holds, to find where a change belongs.
-
Open draft pull requests
On a new branch against the default branch, saying what changed, why, and which tests ran.
-
Push follow-up commits
Onto its own branch only, and only as a fast-forward.
-
Answer review comments
Each in its own thread, saying what it did about it or why it changed nothing.
-
Review pull requests on request
One set of comments, on the whole change and on each line a finding is about.
-
Acknowledge a mention
A 👀 reaction when someone mentions its App, before the work starts.
-
Follow the pull request to the end
A merge settles the Task. Closing it without merging puts the Task back to Needs your input.
How teams use it
-
Turn a request into a draft pull request
Give Jigward a Task from Slack, Jira, a Chat or the web app. When the work changes code, it arrives as a draft pull request with how it was checked.
For example: The CSV export drops rows with an empty region. Can you fix it?
-
Have review comments addressed
Review it as you would a colleague's. Jigward works on the same branch, updates the same pull request, and answers every comment where it was left.
For example: This should reuse the existing retry helper.
-
Get a first review on any pull request
Request Jigward's review, or mention its App on a pull request. A second request on the same pull request knows what the first review said.
For example: Can you check the migration in this one?
What you need
- A Jigward organization, and an admin in it to connect GitHub.
- A GitHub account or organization where you can install a GitHub App.
Connecting it
- An admin opens Integrations in Jigward and connects GitHub.
- On GitHub, install the Jigward App and choose its repositories. You can change them there at any time.
- Add each repository to a Context, so its Tasks, Chats and knowledge stay together.
Security and access
| Permission | Access | Why Jigward needs it |
|---|---|---|
| Contents | Read and write | To read the code, and to commit a change to a branch of its own. |
| Pull requests | Read and write | To open draft pull requests, read their reviews, and post its answers and reviews. |
| Issues | Read and write | GitHub files a pull request's conversation comments here; Jigward reads them and reacts to a mention. |
| Metadata | Read | To see the repositories it was given, and to check that whoever asks can write to one. |
Workflows, Checks and Commit statuses are not asked for, so Jigward cannot change a file in .github/workflows/ and does not read check runs.
-
You choose the repositories
Installing the App is what grants access, on GitHub's own screen. Jigward sees only the repositories you grant it there.
-
Only an admin connects it
Connecting GitHub needs an admin of your Jigward organization, and the installation is checked against that person's own GitHub installations before it is saved.
-
One installation, one organization
An installation belongs to exactly one Jigward organization, and GitHub's events reach only that organization.
-
Tokens scoped to one repository
Every write asks GitHub for an installation token limited to that repository and to the permissions the write needs.
-
No credentials where the code runs
A Task changes code in a workspace of its own, a separate microVM. Repository code runs there as an unprivileged user, with no credential of any kind, and can reach the internet as a build fetching its dependencies has to.
-
Signed events only
Every event GitHub sends is checked against the App's HMAC-SHA256 signature before it is read.
-
Only people who can write may ask
A review is started only by someone GitHub says can write to the repository. A pull request nobody asked about is not reviewed.
-
Your workflows still run
Jigward's branch lives in your repository, so your own workflows run on it, with the repository's secrets, as on any branch.
Jigward never does these in GitHub
- Merge a pull request.
- Approve or block one. A review is always posted as a comment, fixed in the code that sends it.
- Push to the default branch, or force-push any branch.
- Resolve a conflict with the base branch on its own.
- Review a pull request nobody asked it to.
Other integrations
GitHub is a trademark of its owner, and naming it does not mean it endorses Jigward. GitHub and the Invertocat logo are trademarks of GitHub, Inc.
Meet your next engineering coworker
Bring a question
from your own project.
See how Jigward can help your team understand the system and move the next task forward.
Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.