Reusable GitHub Actions Workflows

This repository contains reusable GitHub Actions workflows to automate development workflows and team communication across glocurrency repositories.

---

Table of Contents

• 1. Assign Reviewer (assign-reviewer.yml)
• 2. Alert QA (alert-qa.yml)
• 3. Gemini Review (gemini-review.yml)

---

Reusable Workflows

1. Assign Reviewer (assign-reviewer.yml)

Automatically assigns reviewers to a Pull Request (PR) and notifies them on Telegram.

Features

• Skips execution if the branch starts with release-.
• Only runs if no reviewers have been assigned/reviewed yet.
• Translates GitHub usernames to Telegram handles dynamically using a JSON-formatted secret mapping.

Inputs

Name	Type	Required	Default	Description
config-path	string	No	'.github/assign-config.yml'	Path to the reviewer configuration file.

Secrets

Name	Required	Description
telegram-token	Yes	Telegram Bot token used to send notifications.
telegram-chat-id	Yes	Telegram Chat ID where notifications are sent.
telegram-usernames	No	JSON string mapping GitHub to Telegram handles (e.g. {"github_user": "@telegram_user"}).

Setup & Prerequisites

You must create a configuration file (e.g., .github/assign-config.yml) in your repository for auto-assign-action:

# .github/assign-config.yml
addReviewers: true
addAssignees: false
reviewers:
  - github_user1
  - github_user2
numberOfReviewers: 1

Usage Example

name: Auto Assign Reviewers

on:
  pull_request:
    types: [opened, ready_for_review]

jobs:
  assign-and-notify:
    uses: glocurrency/reusable-actions/.github/workflows/assign-reviewer.yml@main
    with:
      config-path: '.github/assign-config.yml'
    secrets:
      telegram-token: ${{ secrets.TELEGRAM_TOKEN }}
      telegram-chat-id: ${{ secrets.TELEGRAM_CHAT_ID }}
      telegram-usernames: '{"github_user1": "@telegram_handle1", "github_user2": "@telegram_handle2"}'

---

2. Alert QA (alert-qa.yml)

Sends structured build/test alerts to Telegram and randomly tags a QA engineer from a configured team list.

Features

• Randomly tags a QA engineer from a provided JSON array.
• Sets a green prefix (✅ OK) for 'success' status and red prefix (🚨 Alert) for 'failure'.
• Uses HTML formatting in Telegram messages.

Inputs

Name	Type	Required	Default	Description
message	string	Yes	—	Message body text to send.
status	string	No	'failure'	Job status ('success' or 'failure') to format the alert prefix.

Secrets

Name	Required	Description
telegram-token	Yes	Telegram Bot token used to send notifications.
telegram-chat-id	Yes	Telegram Chat ID where notifications are sent.
telegram-qa-usernames	No	JSON array of QA Telegram handles (e.g., ["@qa_alice", "@qa_bob"]). Falls back to notifying "QA Team" if not provided.

Usage Example

name: Continuous Integration

on:
  push:
    branches: [main]

jobs:
  build-and-test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v4
      - name: Run Tests
        run: npm test

  notify-qa-success:
    needs: build-and-test
    if: success()
    uses: glocurrency/reusable-actions/.github/workflows/alert-qa.yml@main
    with:
      status: 'success'
      message: 'Build and unit tests passed on main!'
    secrets:
      telegram-token: ${{ secrets.TELEGRAM_TOKEN }}
      telegram-chat-id: ${{ secrets.TELEGRAM_CHAT_ID }}
      telegram-qa-usernames: '["@qa_alice", "@qa_bob"]'

  notify-qa-failure:
    needs: build-and-test
    if: failure()
    uses: glocurrency/reusable-actions/.github/workflows/alert-qa.yml@main
    with:
      status: 'failure'
      message: 'Build or tests failed on main.'
    secrets:
      telegram-token: ${{ secrets.TELEGRAM_TOKEN }}
      telegram-chat-id: ${{ secrets.TELEGRAM_CHAT_ID }}
      telegram-qa-usernames: '["@qa_alice", "@qa_bob"]'

---

3. Gemini Review (gemini-review.yml)

Automatically reviews Pull Requests using the Gemini Pro API model via Google's Gemini CLI extension system, posting automated review feedback comments directly to the PR.

Features

• Posts an acknowledgement comment when starting the analysis.
• Automatically mints a short-lived GitHub App installation token for secure repository and PR interactions.
• Runs the Gemini CLI tool configured with a GitHub Model Context Protocol (MCP) server running in Docker, allowing Gemini to inspect files and write comments/pending reviews.
• Cleans up transient status/error comments upon workflow completion or failure, ensuring a tidy PR conversation.
• Reports detailed error messages back to the PR if the review fails.

Inputs

Name	Type	Required	Default	Description
prompt-path	string	No	'.github/commands/gemini-review.toml'	Path to the Gemini CLI review configuration/prompt file in the caller repository.

Secrets

Name	Required	Description
reviewer-app-id	Yes	GitHub App ID used to mint the identity token for review comments.
reviewer-private-key	Yes	GitHub App Private Key used to mint the identity token.
gemini-api-key	Yes	API key used to authenticate with Google's Gemini API.

Setup & Prerequisites

Your calling repository must contain the prompt configuration file referenced by prompt-path (defaults to .github/commands/gemini-review.toml). Example of a .github/commands/gemini-review.toml file:

# .github/commands/gemini-review.toml
# Gemini Review configuration
[prompt]
system = """
You are a senior software engineer and security auditor.
Your job is to review the code changes in this Pull Request, identify bugs, security vulnerabilities, or performance issues, and suggest clear, actionable improvements.
"""

You also need a GitHub App with permissions for Contents: read, Issues: write, and Pull Requests: write to mint the identity token.

Usage Example

name: '🤖 gemini'

on:
  pull_request:
    types: [opened, synchronize, reopened]

jobs:
  review:
    uses: glocurrency/reusable-actions/.github/workflows/gemini-review.yml@main
    with:
      prompt-path: '.github/commands/gemini-review.toml'
    secrets:
      reviewer-app-id: ${{ secrets.REVIEWER_APPID }}
      reviewer-private-key: ${{ secrets.REVIEWER_PRIVATE_TOKEN }}
      gemini-api-key: ${{ secrets.GEMINI_API_KEY }}