Netlify

Connect Netlify and every deploy of a linked site shows up where your team is already looking: on the card of the pull or merge request it was built from, and on issues whose key is in the branch name. Finished production deploys can be posted to a chat channel. Open Integrations → Netlify → Configure to set it up. You need permission to manage integrations.

Connecting Netlify

There are two ways to connect:

• Connect Netlify signs in with your Netlify account (where available).
• Access token works everywhere. Create a personal access token in Netlify's User settings → Applications → Personal access tokens and paste it in.

Linking sites

Under Sites, search for a Netlify site and choose Link. Deckbell adds deploy notifications (deploy started, succeeded and failed) to the site. Each notification is signed with a secret only Deckbell and Netlify know; anything else is ignored. For each linked site you can pick:

• Deckbell project: deploys are only listed on issues of this project. Leave it on Any project to match issues anywhere in the workspace.
• Post production deploys to: a channel that gets a message when a production deploy finishes (with the site's address) or fails (with a link to the deploy log). Deploy previews and branch deploys aren't posted.

Unlink removes the site and its notifications. Disconnect removes Netlify from the workspace.

Deploy previews on pull requests and issues

Deckbell matches each deploy to the pull or merge request whose latest commit or branch it built. The request's card on the issue then shows Preview building, Preview ready (click to open the deploy preview) or Deploy failed (click for the deploy log). Pull request cards that agents post in chat show the same badges.

Deploys of a branch that names an issue (like hrb-142-proration) but has no linked pull request are listed under Deployments on that issue.