Reusable Workflows

Set of reusable workflows, as proposed in these YouTube videos:

• GitHub Actions Reusable Workflows FULL TUTORIAL with Examples: Templates on Steroids
• GitHub Actions - Calling Reusable Workflows

When a reusable workfows is created its documentation must be added below and the secrets must be well designed to avoid "invalid secret, is not defined in the referenced workflow".

Add project to issues

This reusable workflos was created to automate the process of vinculate a project to a new issue.

The following configurations must be done in the repo that will call this reusable workflow:

• GitHub secrets:

  • GH_TOKEN, as explained here.
  • USER;
  • TYPE - users or orgs; and
  • PROJECT_NUMBER; and

• Create the file .github/workflow/add_project_to_issue.yml with the content below:

# This uses a reusable workflow
name: Reusable Workflow to add a project to issues

on:
  issues:
    types: [opened]

jobs:
  do-it:
    uses: gabrielbdornas/reusable-workflows/.github/workflows/add_project_to_issue_reusable.yml@main
    secrets:
        GH_TOKEN: ${{ secrets.GH_TOKEN }}
        USER: ${{ secrets.USER }}
        TYPE: ${{ secrets.TYPE }}
        PROJECT_NUMBER: ${{ secrets.PROJECT_NUMBER }}

Add assignee to issue

This reusable workflos was created to automate the process of set assignee to a GitHub issue. It'll link the issue's creator as assignee.

The following configurations must be done in the repo that will call this reusable workflow:

• GitHub secrets:

  • GH_TOKEN

• Create the file .github/workflow/add_assignee_to_issue_reusable.yml with the content below:

# This uses a reusable workflow
name: Reusable Workflow to add a assignee to issues

on:
  issues:
    types: [opened]

jobs:
  do-it:
    uses: ./.github/workflows/add_assignee_to_issue_reusable.yml
    secrets:
        GH_TOKEN: ${{ secrets.GH_TOKEN }}

Add duo date to users closed issue

This reusable workflos was created to automate the process of set duo date to closed issues linked to a GitHub project.

The following configurations must be done in the repo that will call this reusable workflow:

• GitHub secrets:

  • USER;
  • PROJECT_NUMBER; and
  • GH_TOKEN

• Create the file .github/workflow/set_due_date_to_users_closed_issue.yml with the content below:

# This uses a reusable workflow
name: Reusable Workflow to set due date to closed issue

on:
  issues:
    types: [closed]

jobs:
  do-it:
    uses: gabrielbdornas/reusable-workflows/.github/workflows/set_due_date_to_users_closed_issue_reusable.yml@main
    secrets:
        GH_TOKEN: ${{ secrets.GH_TOKEN }}
        USER: ${{ secrets.USER }}
        PROJECT_NUMBER: ${{ secrets.PROJECT_NUMBER }}

Add duo date to orgs closed issue

This reusable workflos was created to automate the process of set duo date to closed issues linked to a GitHub project.

The following configurations must be done in the repo that will call this reusable workflow:

• GitHub secrets:

  • USER;
  • PROJECT_NUMBER; and
  • GH_TOKEN

• Create the file .github/workflow/set_due_date_to_orgs_closed_issue.yml with the content below:

# This uses a reusable workflow
name: Reusable Workflow to set due date to closed issue

on:
  issues:
    types: [closed]

jobs:
  do-it:
    uses: gabrielbdornas/reusable-workflows/.github/workflows/set_due_date_to_orgs_closed_issue_reusable.yml@main
    secrets:
        GH_TOKEN: ${{ secrets.GH_TOKEN }}
        USER: ${{ secrets.USER }}
        PROJECT_NUMBER: ${{ secrets.PROJECT_NUMBER }}