Setup

Now that you've finished installing your integrations, there are a few important steps left to ensure everything works smoothly:

Map Git ↔ Slack users

For Pullpo to coordinate data across integrations, you'll need to map each Git user to their corresponding Slack user. You'll want to do this Git ↔ Slack association as soon as possible to enable:

• Fully synchronized PR channels on Slack, inviting all desired members. Including all messages, code comments and thread responses.
• Alerts on workflow results, mergeability status changes, approvals, change-requests, new commits and more.
• DevEx surveys and instant-feedback requests delivered to the right person, at the right time.
• Git actions, performed in Slack: such as assigning reviewers or approving pull requests.

Head over to the People tab to manually map your team members. If you chose to send the Welcome message to everyone in Slack during the installation, developers in your organization may gradually sign up and get automatically mapped.

Create squads

Group team members who regularly collaborate into squads. This lets you track and compare metrics at the squad level, and define objectives that trigger alerts, scheduled reminders and DevEx feedback requests.

Head to the Squads tab and create your first squad by clicking the 'Add squad' button:

• [Required] Add members manually or import your GitHub teams directly (GitHub only).
• Limit squad metrics to activity in specific repositories.
• Set a Slack channel to receive weekly engineering summaries, dynamic PR-Status messages, and more.
• Define metric-based objectives to trigger reminders that keep the team on track and collect feedback when deviations occur.

Find what works and what doesn't, and share the findings with your other squads to collectively level up your development team.

Enable stability metrics

Stability metrics like Change Failure Rate (CFR) and Mean Time To Restore (MTTR) are calculated based on deployments that represent a fix to a previous incident. If you visit the Metrics tab you'll see a section missing, click on 'Set-up detection rules' to tell Pullpo how to detect these deployment failures.

An example of a set of detection rules could be:

The defined rule set applies to all squads. When updating it, you can choose to 'Recompute historic data', which will overwrite existing deployment failures by applying the new rules to past PR deployments. Note that old push-to-main deployments are not included in this recalculation.

Review access settings

When team members sign up to Pullpo through one of your installed integrations, they'll receive the dashboard access scopes defined in your 'New Sign-ups Policies'. Make sure these policies match your team's needs. By default:

• Users signing in via your Git provider are granted READ_ALL and WRITE_ALL permissions.
• Users signing in via Slack receive READ_ALL permissions only.

You can also generate custom invite URLs to assign specific permissions to new members. For example, you may want to grant ADMIN privileges to someone else to help manage team permissions.

Currently, there are three permission levels (more granular options will be added in the future):

All users who have accessed your team's dashboard will appear in a table showing their current permissions, along with indicators for the owner and biller of your organization.