How to connect GitHub to Layerdock

Once GitHub is connected, every new pin becomes an issue in the repository you choose, carrying the screenshot, page URL, CSS selector, viewport and the reporter's browser and OS. Close the issue and the pin resolves itself.

Before you start

Permission to install a GitHub App on the account or organisation that owns the repository. On an org you may need an admin to approve it, and on some orgs the request goes into a queue.

Connect it

1. Open the GitHub page

In Layerdock, go to Integrations → GitHub. Click Connect a dock, choose the dock, then Continue to GitHub.

2. Choose where to install

GitHub asks which account or organisation to install into. Then choose Only select repositoriesand pick the ones Layerdock may use. Granting all repositories works but gives access far beyond what is needed — the app only ever reads and writes issues.

3. Pick a repository

You come back to Layerdock. Click Choose a repositoryon the dock's row and pick one. The install screen decides which repos the app can see, never which one to post into, so this second step is not optional.

That list is fetched live every time rather than cached: access can be revoked in GitHub without anyone returning here, and a stale list would offer repositories that 404 on the first delivery. Archived repos and repos with issues disabled are hidden, since they would accept the connection and then reject everything.

4. Test

Click Test. An issue should appear within a few seconds, labelled layerdock.

Two-way sync

Per repository, so the person who owns it does this part:

1. Repo → Settings → Webhooks → Add webhook
2. Payload URL: https://www.layerdock.io/api/webhooks/github
3. Content type: application/json
4. Secret: a random string, which also goes in GITHUB_WEBHOOK_SECRET on the deployment
5. Events: Let me select individual events → Issues only

Closing an issue resolves the pin. Reopening it moves the pin back to open.

Good to know

It is a GitHub App, not a personal access token. A token belongs to one person and stops working when they leave or when it expires. The App keeps working, and its reach is limited to issues on the repositories you picked.

The screenshot is a link, not an upload. GitHub has no public API for attaching a file to an issue, so this is the only approach available. The image is served from Layerdock.

Only new pins open issues. Replies and status changes do not edit an existing issue.

If it stops working

Reconnect needed means the App was uninstalled or lost access to the repo. Click Reconnect and reinstall.

If issues stop appearing with no warning shown, check the repository has not been archived and that issues are still enabled — both look like silence rather than a failure.

Working from your editor? Connect your coding agent to read and close pins over MCP, or see all documentation.