CI artifact completeness gate (Git push, Sentry artifact verification, commit)

CI Artifact Completeness Gate (GitHub Push → Sentry Release Files → Artifact Validation → GitHub Commit Status Update)

This workflow acts as a CI/CD quality gate for mobile app crash-symbolication artifacts. Whenever a new commit is pushed to GitHub, the workflow automatically checks the corresponding Sentry release and confirms whether required build artifacts (dSYM or ProGuard + mapping.txt) exist. If artifacts are complete, it updates the GitHub commit status to success, allowing the PR to be merged. If incomplete, the workflow fails silently (no commit status update), effectively blocking merges.

⚡ Quick Implementation Steps

1. Configure GitHub Trigger for your repo. 2. Add Sentry API credentials. 3. Add GitHub API credentials. 4. Update Sentry project URLs with your orgslug and projslug. 5. Ensure your build pipeline uploads artifacts to Sentry before the workflow runs. 6. Activate workflow.

What It Does

This workflow ensures your mobile crash-symbolication artifacts are fully present in Sentry for every release.

When a new GitHub push occurs, the workflow:

1. Reads the commit SHA and repo info from the GitHub Push event. 2. Fetches the list of all releases from Sentry. 3. Locates the correct release and fetches its uploaded artifact files. 4. Runs custom validation logic: - Success if: - a .dSYM file exists OR\ - both proguard.txt AND mapping.txt are present\ - Failure if: - neither dSYM nor both mapping artifacts exist. 5. If validated successfully, the commit receives a success status on GitHub → PR can be merged.