vault/.github/workflows/milestone-checker.yml
Vault Automation 94b4d7ca17
actions: use self-hosted runners in hashicorp/vault-enterprise (#9664) (#9683)
* actions: use self-hosted runners in hashicorp/vault

While it is recommended that we use self-hosted runners for every
workflow in private and internal accounts, this change was primarily
motivated by different runner types using different cache paths. By
using the same runner type everywhere we can avoid double caches of the
internal Vault tools.

* disable the terraform wrapper in ci-bootstrap to handle updated action

Signed-off-by: Ryan Cragun <me@ryan.ec>
Co-authored-by: Ryan Cragun <me@ryan.ec>
2025-09-26 10:12:43 -06:00

26 lines
1.2 KiB
YAML

# This workflow checks that there is either a 'pr/no-milestone' label applied to a PR
# or there is a milestone associated with a PR
name: Check Milestone
on:
pull_request:
# milestoned and demilestoned work (https://github.com/github/docs/issues/23909) but they aren't listed in the github documentation
types: [opened, synchronize, labeled, unlabeled, milestoned, demilestoned]
# Runs on PRs to main and release branches
branches:
- main
- release/**
- ce/**
jobs:
# checks that a milestone entry is present for a PR
milestone-check:
# If there is a `pr/no-milestone` label, or this comes from a fork (community contributor) we ignore this check
if: ${{ ((github.repository == 'hashicorp/vault' || github.repository == 'hashicorp/vault-enterprise')
&& (github.event.pull_request.head.repo.full_name == github.event.pull_request.base.repo.full_name))
&& (!contains(github.event.pull_request.labels.*.name, 'pr/no-milestone')) }}
runs-on: ${{ github.repository == 'hashicorp/vault' && 'ubuntu-latest' || fromJSON('["self-hosted","ubuntu-latest-x64"]') }}
steps:
- name: Check milestone
run: ${{ github.event.pull_request.milestone != null }}