Mark releases
Mark every deploy, and Fidiba can say which release started a problem: "new in 3f1c2a0" is one click away.
One line in your deploy
curl -X POST https://in.fidiba.dev/31/releases \ -H "Authorization: Bearer KEY" \ -d version="$GIT_SHA"
Use the same version you give the Sentry SDK as release, so errors and releases line up.
In GitHub Actions
- name: Tell Fidiba about the release
run: |
curl -fsS -X POST https://in.fidiba.dev/31/releases \
-H "Authorization: Bearer ${{ secrets.FIDIBA_WRITE_KEY }}" \
-d version="${{ github.sha }}"What you get
Each release shows on the outline and on every chart. Thirty minutes after a release, Fidiba says whether it made things better, worse or the same.