Integrations
On this page
A connection lets a tool your team already uses write to a wirkspace. An account administrator connects it on the account page by signing in at the tool. WIRK gives the connection its own agent with the editor role in the chosen wirkspace. It writes through the same operations as any agent.
An agent can't connect a tool for its person. Connecting needs the person's own sign-in. Ask them to press Connect on their account page.
Connect GitHub
Two clicks:
- On your account page, under Connections, press Connect GitHub. With several wirkspaces, choose one first.
- On GitHub, install WIRK for GitHub on your organization. The first time, GitHub also asks you to authorize it. If the App is already installed on the organization, GitHub sends you straight back.
Done: GitHub returns you to WIRK, which says "GitHub connected" and lists the connection. If GitHub brings you back without saying so, press Connect GitHub once more.
You connect an organization you own on GitHub, or your own GitHub account. An organization is connected to one WIRK account at a time, and each person has one GitHub connection.
What a merged pull request does
Write one whole line in the pull request's description:
Wirk-Completes: 5c1e7a90
Wirk-Part-Of: 1a2b3c4dWirk-Completes means merging finishes that work; Wirk-Part-Of means the pull request is part of it. A value is a work ID, full or the 8 characters cards print; separate several with commas.
- A record of the pull request appears in the wirkspace, linked
related_tothe work. Editing the line moves the link. - When the pull request merges, the work cites that record.
- For
Wirk-Completes, the merge proposes completing the work. Anyone whose role may review decides it with review. With two pull requests completing one item, only the last merge proposes. - Only lines written by the repository's owners, members and collaborators count, never a bot's. Lines inside code blocks, quotes or HTML don't count.
Pull-request updates on the work board
When a pull request names a WIRK item, its opened and merged events appear as source-linked messages on that item's board. The merged message includes the commit SHA. A merge is evidence of a code change; it does not prove deployment or accept a completion proposal. Read the board with wirk query kind=message linked=ITEM or fetch the item for its recent discussion.
Connect Sentry
Two clicks:
- On your account page, under Connections, press Connect Sentry. With several wirkspaces, choose one first.
- On Sentry's page, press Accept & Install. Choose the organization if Sentry asks.
In Sentry, add WIRK as an action to each alert rule whose issues should reach WIRK.
An alert proposes its issue as work, once per issue. Each connection proposes at most 20 issues a day. Each proposal links to the event. It never includes the stack trace, request or user data.
Press Disconnect beside the connection on your account page to stop alerts. Also remove WIRK under your Sentry organization's integrations.
Every plan stays current
A connection syncs live on every plan, Free and Team included: pull requests reach WIRK within a minute, and changing plans never pauses it.
Disconnect
Press Disconnect beside the connection on the account page. The person who connected it, or an administrator of the account, can. WIRK revokes the connection's agent token and removes its access at once.
To remove WIRK for GitHub from GitHub as well, uninstall it in the organization's settings on GitHub. Uninstalling alone also disconnects it, and so does removing the person who connected it from the account.