mirror of
https://github.com/carbon-language/carbon-lang.git
synced 2026-11-10 12:28:25 +00:00
Chandler Carruth
a50feb64ce
We now only use a single `proposal` label on proposal PRs rather than separate state labels (`proposal draft`, `proposal rfc`, `proposal accepted`, `proposal declined`, and `proposal deferred`), as draft, open, merged, and closed PR states already capture the proposal lifecycle. - Remove the `proposal_labeled.yaml` and `proposal_ready.yaml` workflows. - Update `new_proposal.py`, `template.md`, `evolution.md`, and `CONTRIBUTING.md` to only use the `proposal` label and filter non-draft proposal PRs with `draft:false`. - Fix `auto_label_prs.yaml` to apply the `bot` label instead of the non-existent `automated` label and fix the `proposals/scripts/**` path filter typo. - Update `triage_inactive.yaml` to exempt `needs design doc update` instead of the old `design update` label. Assisted-by: Antigravity with Gemini
65 lines
2.4 KiB
YAML
65 lines
2.4 KiB
YAML
# Part of the Carbon Language project, under the Apache License v2.0 with LLVM
|
|
# Exceptions. See /LICENSE for license information.
|
|
# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
|
|
name: 'Triage inactive issues and PRs'
|
|
on:
|
|
schedule:
|
|
- cron: '30 1 * * *'
|
|
|
|
permissions:
|
|
issues: write # For actions/stale to close stale issues.
|
|
pull-requests: write # For actions/stale to close stale PRs.
|
|
|
|
jobs:
|
|
stale:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Harden Runner
|
|
uses: step-security/harden-runner@e14015d583714f6e62063499dc959a02595150a1 # v2.21.1
|
|
with:
|
|
disable-sudo: true
|
|
egress-policy: block
|
|
# prettier-ignore
|
|
allowed-endpoints: >
|
|
api.github.com:443
|
|
|
|
- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9.0.0
|
|
with:
|
|
stale-issue-message: >
|
|
We triage inactive PRs and issues in order to make it easier to find
|
|
active work. If this issue should remain active or becomes active
|
|
again, please comment or remove the `inactive` label. The `long term
|
|
issue` label can also be added for issues which are expected to take
|
|
time.
|
|
|
|
|
|
This issue is labeled `inactive` because the last activity was over
|
|
90 days ago.
|
|
stale-pr-message: >
|
|
We triage inactive PRs and issues in order to make it easier to find
|
|
active work. If this PR should remain active, please comment or
|
|
remove the `inactive` label.
|
|
|
|
|
|
This PR is labeled `inactive` because the last activity was over 90
|
|
days ago. This PR will be closed and archived after 14 additional
|
|
days without activity.
|
|
close-pr-message: >
|
|
We triage inactive PRs and issues in order to make it easier to find
|
|
active work. If this PR should remain active or becomes active
|
|
again, please reopen it.
|
|
|
|
|
|
This PR was closed and archived because there has been no new
|
|
activity in the 14 days since the `inactive` label was added.
|
|
stale-issue-label: 'inactive'
|
|
stale-pr-label: 'inactive'
|
|
exempt-issue-labels:
|
|
'long term issue,design idea,needs design doc update,good first
|
|
issue,leads question'
|
|
days-before-stale: 90
|
|
days-before-close: 14
|
|
days-before-issue-close: -1
|
|
operations-per-run: 100
|