Integration
Sitejar GitHub integration
The Sitejar GitHub integration turns website scan findings into GitHub issues in the repository you choose, one issue per finding and never a duplicate: sending a finding again adds a comment to the issue it already has. Each issue carries the rule, the severity, the pages it was found on and the suggested fix, its state shows on the finding in Sitejar, and only a scan that no longer detects the problem marks it fixed.
On Pro and above.
What the Sitejar GitHub integration does
Sitejar scans a site in a real browser for accessibility (WCAG 2.1 AA), security, privacy, deceptive design, technical quality and SEO, and tracks each problem from scan to scan. This integration carries those findings to where your team plans its work, written so whoever picks one up can start without opening Sitejar.
- One issue per finding. Sending it again adds a comment instead of a second issue.
- The issue's state, read back from GitHub, shows on the finding.
- A default repository for the workspace, and its own repository for any site that needs one.
- Whole reports in one send: a GitHub issue for the report whose body ends with a task list linking every finding's issue.
Who the GitHub integration is for
Teams that already plan their work in GitHub and want website problems in the same queue as everything else. If your developers work from GitHub issues, findings land next to the code they concern, in the repository that builds the site, where an issue can be referenced from the pull request that fixes it. It suits agencies handing client fixes to a delivery team, and developers who would rather get an issue with a selector and a fix than a PDF.
Send accessibility issues to GitHub
Accessibility is the most common reason teams send findings, but any finding can go: a missing security header, a tracker that loads before consent, a broken link.
Turn a new scan into a backlog
Send a whole report and Sitejar creates a GitHub issue for the report whose body ends with a task list linking every finding's issue, most severe first, filtered by severity and with or without Needs review findings. Send the same report again later and only the findings not yet sent are added.
Send just what fits this sprint
Select a handful of findings on the Findings page, or open one finding, and send only those. The rest stay in Sitejar until you are ready.
Keep each client's work in its own repository
Give a site its own destination, and its findings go to that repository while everything else goes to the default. On Agency Plus, a client can have a destination too: a site's own wins over its client's, and its client's over the default.
How to connect GitHub to Sitejar
- Sign in to Sitejar as an Owner or Admin of the workspace and open Settings, then Integrations.
- On the GitHub card, choose "Connect GitHub". If your plan does not include GitHub, the card says "Not on your plan" instead.
- GitHub opens the install page of the Sitejar GitHub App. Choose the organization or personal account, then all repositories or only the ones you select, and install.
- GitHub then asks you to authorize the app. That step is how Sitejar confirms your GitHub account can manage the installation it is about to connect, so a pasted installation id from someone else's organization is refused.
- If you are a member of a GitHub organization but not an owner, GitHub sends an install request to the owners instead. Sitejar tells you the request went to them, and the connection completes when an owner approves it.
- Back in Sitejar, the card says "Connected to" followed by the GitHub organization or account the app is installed on. Under "Tasks go to", choose the repository new issues go to by default.
- Optional: under "Give a site its own destination", pick a site and a repository, then choose "Add".
A workspace has one GitHub connection, and connecting again replaces it.
How to send findings to GitHub
Anyone whose role can manage findings (Owner, Admin or Editor) can send them, three ways:
- On the Findings page, select findings and choose "Send to GitHub" in the bulk actions bar, or choose "Create tasks" and pick GitHub under "Send to". Up to 50 at a time.
- On one finding, use "Send to GitHub" in its Task section, which then links to the issue.
- On a report, choose "Send report to GitHub" in the Next steps panel ("Send report to a task tool" when more than one is connected), pick the severities, and send. Up to 100 issues at a time.
What Sitejar sends to GitHub, and what it stores
What a GitHub issue from Sitejar contains
The title names the dimension, the severity, the rule, the page count and the site: [Accessibility][High] Form field missing a label (12 pages) | example.com.
The body carries the confidence label (Confirmed, Likely or Needs review), how many instances on how many pages and the scan date, a CSS selector, the WCAG success criterion where one applies, the first 20 page urls, the suggested fix and its code when one exists (or "No AI fix yet"), and a link back to the finding. It never contains evidence captured from your pages or their content. GitHub renders the body as Markdown, so the selector and any suggested code read as code.
Permissions Sitejar asks for in GitHub
The Sitejar GitHub App asks for two permissions on the repositories you install it on: Issues (read and write) and Metadata (read), the second of which GitHub requires of every app. It does not ask for code, pull requests, Actions or anything else.
Sitejar stores no GitHub token at all. It keeps the installation id, and each time it needs GitHub it creates a short-lived installation token, signed with the app's private key, and uses it for that one call.
What Sitejar stores about your GitHub connection
Sitejar stores no GitHub token at all (it creates a short-lived one for each call), the GitHub organization or account the app is installed on for the card, the installation id, and the last error GitHub returned. Credentials are encrypted with AES-256-GCM and never sent to your browser. For each issue it created, Sitejar keeps the issue's id, url, last state and when it last checked. If you install the app on a personal account, the label on the card is your GitHub username. That is the only personal data Sitejar keeps from GitHub. It never reads your code, other issues or your members.
Disconnecting empties the stored credentials at once, and the issues already created stay in GitHub. To revoke the grant on the GitHub side too, remove Sitejar in GitHub's own settings.
What happens in GitHub after the next scan
The sync runs one way: a scan can move an issue, but closing an issue never marks a finding fixed. Only a scan that no longer detects the problem does, so a issue closed by mistake or before the deploy cannot flatter your scores.
When a linked issue is shown in Sitejar, Sitejar reads its state from GitHub, at most once every 10 minutes. The finding shows Open or Closed, exactly as GitHub reports the issue. If GitHub answers with an error, the last known state stays. Issues deleted in GitHub show as Removed, and one closed while the latest scan still finds the problem shows "Reopened: closed in the tool, still detected in the latest scan."
On Business and above, each completed scan adds one comment to every linked issue: "Still detected in the Sitejar scan of 3 November 2026." or "Not detected in the Sitejar scan of 3 November 2026. A scan, not this task, confirms a fix."
On Agency Plus, you can turn on "Move tasks after each scan" on the GitHub card. Issues whose finding is not detected then move to closed, with the reason "completed", and those whose finding comes back move to open again. It is off until you turn it on.
Which plans include the GitHub integration, and its limits
GitHub is on Pro and above. Whole-report sends and after-scan comments are on Business and above, and automatic moves and per-client destinations are on Agency Plus. To see everything each plan includes, compare plans on the pricing page.
- One GitHub connection per workspace.
- Up to 50 findings per send from the findings list, and up to 100 issues per whole-report send. Send the report again for the rest.
- The first 100 repositories the installation can reach are offered as destinations.
- Repositories are only those you gave the app access to when you installed it. Change that list in GitHub, not in Sitejar.
- Dedupe belongs to the connection: findings sent through a connection you have since replaced go out as new issues.
Troubleshooting the GitHub integration
"That connection link expired or was already used"
The link GitHub sends you back with works once, within 10 minutes of choosing Connect. Choose "Connect GitHub" again and finish without a long pause.
"Choose where GitHub tasks go for this site first"
No destination applies to that site yet. Choose a default under "Tasks go to", or give the site its own.
The card shows "Last attempt" with an error from GitHub
That is what GitHub answered on the last call. "GitHub answered 401" or "403" usually means the access was revoked or the connected account lost access to that repository: connect again, or choose another repository. "GitHub answered 404" usually means it was deleted.
A repository is missing from "Tasks go to"
The list shows the repositories the Sitejar GitHub App was installed on. In GitHub, open the app's installation settings for your organization or account and add the repository, then reload the Integrations page.
The connection fails with "That GitHub installation is not one your GitHub account can manage"
Sitejar connects only an installation the authorizing GitHub user can manage. Ask an owner of the GitHub organization to choose "Connect GitHub" from Sitejar, or to approve your install request.
"That GitHub install link has expired"
If you installed the app from GitHub's own site rather than from Sitejar, the Integrations page has 15 minutes to pick the installation up. After that, choose "Connect GitHub" in Sitejar and GitHub will show the existing installation.
GitHub integration FAQ
Does sending a finding to GitHub twice create two issues?
No. Sitejar links each finding to the issue it created. Sending the same finding again through the same connection adds a dated comment with its current details to that issue.
Does closing the GitHub issue mark the finding fixed in Sitejar?
No. Sitejar shows the issue's state, but a finding counts as fixed only when a scan no longer detects the problem. If the issue is closed while the latest scan still finds it, the finding says it was reopened.
What does Sitejar store from GitHub?
The credentials for the connection, encrypted with AES-256-GCM, the GitHub organization or account the app is installed on, and for each issue it created, its id, url and last known state. Disconnecting deletes the credentials at once.
Which plan do I need for the GitHub integration?
GitHub is on Pro and above. Whole-report sends and after-scan comments are on Business and above, and moving issues automatically after a scan is on Agency Plus.
Can the Sitejar GitHub App read my code?
No. The app asks only for Issues (read and write) and Metadata (read), the second being GitHub's minimum for every app. It cannot read files, pull requests or Actions.
Does the GitHub integration work with private repositories?
Yes. Sitejar can open issues in any repository the installation can reach, private or public. You choose those repositories when you install the app.
Related integrations
Last updated . GitHub and the GitHub logo are trademarks of GitHub, Inc. Sitejar is not affiliated with or endorsed by GitHub, Inc.