ionic-team / bot

The bot for Capacitor repos, implemented using GitHub Actions.

Bot

The bot for Ionic and Capacitor repos, implemented using GitHub Actions.

Config

There are two steps to setting up the configuration for this bot.

Workflow File

Add a GitHub Actions workflow file for the bot (usually .github/workflows/bot.yml).

name: Bot

on:
  push:
  issues:
    types: [opened, edited]
  issue_comment:
    types: [created]

jobs:
  bot:
    name: ${{ github.event_name }}/${{ github.event.action }}
    runs-on: ubuntu-latest
    steps:
      - uses: ionic-team/bot@main
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}

Config File

Though this bot is one GitHub Action, it does many things. Because of this, a separate configuration file is needed specifically for the bot (.github/bot.yml):

tasks:
  - name: remove-label
    on:
      issue_comment:
        types: [created]
    condition: 'payload.issue.number === 1'
    config:
      label: needs-reply
      exclude-labeler: true

The tasks key is an array of tasks, the event that triggers them, and their configuration. Notice how the on block is copied from the workflow file to specify exactly which events triggers which tasks. You can also have a condition expression, the result of which determines if the task is run for a particular event payload.

Tasks

• add-comment: Add a comment to an issue, optionally closing and/or locking the issue
  • comment (string): the comment text
  • close (boolean): if true, close the issue
  • lock (boolean): if true, lock the issue
• add-contributors: Open a PR to modify README.md when a new contributor appears in a base branch
  • base (string): the base branch
  • file (string): the file to edit (usually README.md)
  • commit-message (string): the lodash template for the commit message; properties: base, file
  • exclude-patterns (string array): the patterns for excluding contributors, defaults to excluding users whose usernames end in [bot]
• add-label: Add a label to an issue
  • label (string): the label to add
• add-platform-labels: Parse issue bodies and add labels to issues that have keywords under a Platform header
• remove-label: Remove a label from an issue
  • label (string): the label to remove
  • exclude-labeler (boolean): if true, the label won't be removed if the event actor is the user that added the label
• assign-to-project: Assign an issue or pull request to a project
  • columns (object)
    • issue (number): the project column ID to put issues in
    • pr (number): the project column ID to put pull requests in
    • draft-pr (number): the project column ID to put draft PRs in

Condition Context

There are a variety of variables and functions available in condition expressions.

• payload: the entire event payload
• config: the task configuration
• getTeamMembers(teamSlug: string) => Promise<string[]>: get the usernames of an organization team by slug

bot's Issues

Add PR to project if submitted by select people

It would be nice if the bot could add all PRs by certain people to a project.

Feature List

• close old issues that needed a reply
  • decided to split this out into a stand-alone action because it needed a cron schedule
  • the logic to remove the needs-reply label is here
• add comment when issue is created
  • https://gist.github.com/brandyscarney/ba8d28dd8f76dc3aca80e1f6683a2337
  • could do this when the triage label is added
• add triage label
  • add a comment if there hasn't been activity in X days to remind the humans?
  • could use https://github.com/octokit/request-action for this
• automatically add labels to PRs based on directory
  • https://github.com/actions/labeler
• add a comment based on a label (e.g. help wanted label triggers a comment)
  • https://github.com/marketplace/actions/label-commenter ?
• comment and close issues based on a label added (e.g. support issue)
  • https://github.com/marketplace/actions/label-commenter can also close
• run screenshot
  • no