Skip to content

ci: add GitHub Action to trigger Bitrise crowdin_validator on PRs - #3

Closed
anthonyraj wants to merge 3 commits into
mainfrom
ci/github-triggers-bitrise-validator
Closed

ci: add GitHub Action to trigger Bitrise crowdin_validator on PRs#3
anthonyraj wants to merge 3 commits into
mainfrom
ci/github-triggers-bitrise-validator

Conversation

@anthonyraj

Copy link
Copy Markdown
Collaborator

Summary

  • Bitrise's own GitHub webhook auto-registration is currently blocked for the loop-localization app (register_webhookprovider_reauth_required: "GitHub identity is not available for user"). No webhook exists on this repo yet, so pushes/PRs don't auto-trigger Bitrise builds.
  • This adds a GitHub Actions workflow (.github/workflows/crowdin-validator.yml) that triggers the Bitrise crowdin_validator workflow via the Bitrise API on every PR targeting main, waits for the result, and fails this check if the Bitrise build fails.
  • This is what actually needs to happen for GitHub to block a merge (a required status check), independent of whether Bitrise's own webhook/status-reporting is wired up.

Required follow-up (one-time, self-service)

This PR's check will fail until the BITRISE_API_TOKEN repo secret is added:

  1. Bitrise → Account Settings → Security → Personal access tokens → generate one with access to the loop-localization app (Developer role or higher).
  2. gh secret set BITRISE_API_TOKEN --repo youversion/loop-localization

Once that's added, re-run this PR's check to confirm the bridge works end-to-end.

Test plan

  • Add BITRISE_API_TOKEN repo secret
  • Re-run the "Crowdin validator (Bitrise)" check on this PR and confirm it triggers a real Bitrise build and reports pass/fail back here
  • Once confirmed, optionally add branch protection on main requiring this check before merging

Anthony Raj added 3 commits July 27, 2026 17:42
Bitrise's own GitHub webhook auto-registration is blocked for this app
(needs a GitHub re-auth on the Bitrise account side), so bridge PR
events to the Bitrise crowdin_validator workflow from GitHub Actions
instead: trigger the build via the Bitrise API, wait for it, and fail
this check if it fails.
Bitrise tries to resolve pull_request_repository_url/pull_request_id
against GitHub, which hits the same broken GitHub identity and makes
the trigger call itself fail (HTTP 400: "GitHub identity is not
available for user"). Trigger a plain branch build instead -- the
validator script only does git fetch + diff, it never needs a PR
merge ref. Also switches back to the BITRISE_API_TOKEN secret name.
@anthonyraj
anthonyraj marked this pull request as draft July 28, 2026 03:32
@anthonyraj anthonyraj self-assigned this Jul 28, 2026
@anthonyraj

Copy link
Copy Markdown
Collaborator Author

Closing: Bitrise's native GitHub webhook is now working (reauthorized on Bitrise's side), so it triggers crowdin_validator directly on PR events and reports its own status (ci/bitrise/acab23b7-43de-4110-8288-01fbc83fd63d/pr). This GitHub Actions bridge is redundant -- branch protection on main now requires that native context instead of crowdin_validator.

@anthonyraj anthonyraj closed this Jul 28, 2026
@anthonyraj
anthonyraj deleted the ci/github-triggers-bitrise-validator branch July 28, 2026 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant