Connecting GitHub and your pipelines
Bring code, builds, deployments and security scans into DelPulse, matched to the work they deliver. Video ready
Watch
That is the last video in this track
Well doneYou will be able to
- Set up the code and pipeline connection
- Add the webhook in GitHub, or connect any other tool
- Link repositories to products, teams and projects
- Name the live environments and let pipelines ask the gate
Step by step
- Set up the connection Work › Code and pipelines
DelPulse makes a web address and a secret. Copy the secret straight away: it is shown once. - Add the webhook GitHub › Settings › Webhooks
Pushes, pull requests, workflow runs, deployment statuses, and code scanning, Dependabot and secret scanning alerts. - Link repositories Code and pipelines › Repositories
Each repository to its product, team or project. Developers put the work item key in commits, branches or pull request titles. - Live environments and the gate Code and pipelines › Connection
Name the live environments. Pipelines ask GET /api/v1/devops/gate, with an API token, before deploying.
Try it yourself
Practise as Hannah Lee in the demo.
As an administrator, open Code and pipelines. Which repositories are linked, and to which units?
Open the demo as Hannah Lee Password pulse-demo-2026. The demo resets every night.
The examples use a made-up healthcare organisation. DelPulse is not only for healthcare: it can be set up for any industry, with your own names for every portfolio, programme, product and team.