Ghost/.github/workflows/auto-assign.yml

name: Auto Assign
on:
  pull_request:
    types: [opened, reopened]
jobs:
  automate:
    runs-on: ubuntu-18.04
    if: github.repository_owner == 'TryGhost'
    env:
      FORCE_COLOR: 1
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    steps:
      - uses: actions/checkout@v3
      - run: gh extension install daniellockyer/gh-auto-assign
      - run: gh auto-assign
Added auto-assign workflow to pull requests no issue - Renovate will open PRs to bump dependencies but these are unassigned - Renovate does have the ability to set assignees, but these are blanket assigns not based upon the package that is being upgraded - we want to assign them to the owners of the package that is being upgraded - I've created the `gh-auto-assign` GitHub CLI exntension which reads a `.github/AUTO_ASSIGN` file and assign PRs based upon the entries listed - this commit adds the initial `AUTO_ASSIGN` file and GitHub Actions workflow to trigger when a PR is opened 2021-09-08 12:12:31 +03:00			`name: Auto Assign`
			`on:`
			`pull_request:`
			`types: [opened, reopened]`
			`jobs:`
			`automate:`
			`runs-on: ubuntu-18.04`
Prevented certain GitHub Actions workflows from running on forks fixes https://github.com/TryGhost/Toolbox/issues/285 - without this, some of the workflows that are only useful for the core team will run on forks - this commit adds checks to ensure we're running on a repo maintained by the TryGhost organization for a handful of workflows 2022-06-02 00:54:26 +03:00			`if: github.repository_owner == 'TryGhost'`
Added auto-assign workflow to pull requests no issue - Renovate will open PRs to bump dependencies but these are unassigned - Renovate does have the ability to set assignees, but these are blanket assigns not based upon the package that is being upgraded - we want to assign them to the owners of the package that is being upgraded - I've created the `gh-auto-assign` GitHub CLI exntension which reads a `.github/AUTO_ASSIGN` file and assign PRs based upon the entries listed - this commit adds the initial `AUTO_ASSIGN` file and GitHub Actions workflow to trigger when a PR is opened 2021-09-08 12:12:31 +03:00			`env:`
			`FORCE_COLOR: 1`
Moved `GITHUB_TOKEN` env variable to workflow scope no issue - the CLI install extension step also needs the token so it's just best to include it globally in the workflow 2021-09-09 11:49:08 +03:00			`GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}`
Added auto-assign workflow to pull requests no issue - Renovate will open PRs to bump dependencies but these are unassigned - Renovate does have the ability to set assignees, but these are blanket assigns not based upon the package that is being upgraded - we want to assign them to the owners of the package that is being upgraded - I've created the `gh-auto-assign` GitHub CLI exntension which reads a `.github/AUTO_ASSIGN` file and assign PRs based upon the entries listed - this commit adds the initial `AUTO_ASSIGN` file and GitHub Actions workflow to trigger when a PR is opened 2021-09-08 12:12:31 +03:00			`steps:`
Update actions/checkout action to v3 2022-03-01 21:52:51 +03:00			`- uses: actions/checkout@v3`
Added auto-assign workflow to pull requests no issue - Renovate will open PRs to bump dependencies but these are unassigned - Renovate does have the ability to set assignees, but these are blanket assigns not based upon the package that is being upgraded - we want to assign them to the owners of the package that is being upgraded - I've created the `gh-auto-assign` GitHub CLI exntension which reads a `.github/AUTO_ASSIGN` file and assign PRs based upon the entries listed - this commit adds the initial `AUTO_ASSIGN` file and GitHub Actions workflow to trigger when a PR is opened 2021-09-08 12:12:31 +03:00			`- run: gh extension install daniellockyer/gh-auto-assign`
			`- run: gh auto-assign`