GitHub Project Board

In order to ease up the burden of the project maintainers, there is an internal Project Board on GitHub used to track the progress of the PRs and issues. The board is available only to the @camptocamp/is-devops-stack team and is available here. All the repositories of the DevOps Stack are also connected to this project upon creation.

The way this is accomplished is somewhat convoluted, hence the reason for this documentation page.

DevOps Stack Project

The project itself has been manually created on the @camptocamp organization, using the GitHub web interface (documentation). The project is private (documentation) and only accessible to the @camptocamp/is-devops-stack team (documentation).

All the boards and tables have also been created manually. In the settings of the project, there are automation workflows (documentation) that move the Issues and PRs around depending on their status (open, closed, merged, etc.).

Adding a PR/Issue to the Project

Since there are some limits on how many repositories we can add to a project using the default workflows, we were forced to automate this process using a GitHub workflow, as suggested on the official documentation.

Although the official documentation explicitly calls the API with gh commands, we opted to use an official GitHub Action (actions/add-to-project) to accomplish this. Moreover, in order to allow the workflows to modify the project we needed to create a GitHub app that the sole purpose is providing the necessary permissions to the workflows.

DevOps Stack Project App

The app is called DevOps Stack Project and is available here.

This app was created on our organization by an administrator and is configured with a limited scope of permissions: it can only access the projects of the organization where it is installed as well as the PRs and Issues of repositories on which it is installed (official documentation on how to create a GitHub app).

After the app creation, an administrator was needed to install it on the organization and all the repositories of the DevOps Stack. This was done by going to the app page and clicking on the Install button then configuring the proper settings after installation (all this is done on the organization settings, check the official documentation).

The reason to not install the app on all the repositories by default was to further limit the scope of the app, although this adds the burden of installing it on each repository manually every time a new repository of the DevOps Stack is created.

Centralized workflow

The workflow definition is available in the main repository.

# GitHub Actions workflow to automatically push PRs and issues to the DevOps Stack project board.
# IMPORTANT: This workflow is called by other workflows in our DevOps Stack repositories and it is centralized here in 
# order to be easily maintained across modules. Because of this, please make sure you're not introducing any breaking 
# changes when modifying this workflow.
name: "pr-issues-project"

        description: "GitHub App private key for the DevOps Stack Project app"
        required: true

    - opened
    - reopened
    - opened
    - reopened

    runs-on: ubuntu-latest
    - name: Generate authentication token from GitHub App
      id: generate_token
      uses: tibdex/github-app-token@v2
        app_id: 322306
        private_key: ${{ secrets.PROJECT_APP_PRIVATE_KEY }}

    - name: Add PR or issue to DevOps Stack project board
      uses: actions/add-to-project@v1.0.1
        github-token: ${{ steps.generate_token.outputs.token }}
It is the step Generate authentication token from GitHub App that uses the GitHub app created above in order to generate a token with the proper permissions that is then passed to the Add PR or issue to DevOps Stack project board step.