Deploy feedback
Let your deploy system report back to gittan when a release lands.
What it is
Deploy hooks push outward — gittan tells your deploy system that a new image is ready. Deploy feedback is the return path: your deploy system tells gittan when the release actually landed (or failed).
This closes the loop. Without it, gittan knows a build succeeded but not whether it's running. With it, you get full deployment tracking from commit to production.
How it works
Your deploy system (Flux, ArgoCD, a custom script) sends an HTTP POST to a gittan webhook URL with the deploy status. gittan correlates the status back to the pipeline run that produced the image.
| Direction | Feature | Purpose |
|---|---|---|
| gittan → deploy | Deploy hooks | Trigger deployment |
| deploy → gittan | Deploy feedback | Report deployment result |
Setup
Go to Admin → Deploy feedback. Create a feedback token for each deploy system that should report back. The token is a capability URL — anyone with the token can post status updates, so keep it secret.
Payload formats
POST to https://api.gittan.eu/hooks/deploy/<token> with one of these JSON payloads:
Image-based (e.g. from a deploy script)
{
"image": "images.gittan.eu/acme/api@sha256:abc123...",
"status": "applied"
}Flux Kustomization events are also accepted directly.
Deploy status is shown on pipeline runs and contributes to your team's DORA metrics — specifically deployment frequency and lead time for changes.