Skip to content

Latest commit

 

History

History
52 lines (47 loc) · 2.28 KB

File metadata and controls

52 lines (47 loc) · 2.28 KB

GitHub Actions YAML

Preparation

for Danger

No preparation is required unless you want to use a bot account. If you want to use a bot account, follow the instructions below.

  1. Create a bot account on GitHub.
  2. Add the bot account to the repository as a collaborator.
  3. Create the bot account's personal access token that has full access to repo.
  4. Add the token to GitHub Secrets as DANGER_GITHUB_API_TOKEN.

for Firebase Test Lab

  1. Copy your Firebase Project ID from Firebase Console, and add it to GitHub Secrets as FIREBASE_PROJECT_ID.
  2. Create a service account with an Editor role at https://console.developers.google.com/iam-admin/serviceaccounts
  3. Download a private key for the service account as JSON.
  4. Encode it in Base64 in your favorite way. For example:
cat <private-key>.json | base64
  1. Add the encoded string to GitHub Secrets as SERVICE_ACCOUNT_KEY_BASE64.

for Firebase App Distribution

  1. Copy your Firebase app ID from Firebase Console, and add it to GitHub Secrets as FIREBASE_APP_ID.
  2. Install Firebase CLI on your computer.
  3. Run firebase login:ci on Terminal/Console, and a Firebase token will be printed.
  4. Add the token to GitHub Secrets as FIREBASE_TOKEN.

for Slack

  1. Go to https://slack.com/apps/A0F7XDUAZ-incoming-webhooks
  2. Add Incoming Webhooks
  3. Integration Settings > Post to Channel > (select a channel)
  4. Copy Webhook URL.
  5. Paste it in GitHub Secrets. I name it SLACK_WEBHOOK_URL.

Appendix (optional)

How to use google-services.json securely in a public repository

  1. Download google-services.json from Firebase Console.
  2. Copy the raw content (without being encoded in Base64) to GitHub Secrets as, let's say, GOOGLE_SERVICES_JSON.
  3. Add the following to your workflow.
- run: echo $GOOGLE_SERVICES_JSON > app/google-services.json
  env:
    GOOGLE_SERVICES_JSON: ${{ secrets.GOOGLE_SERVICES_JSON }}