Victor Lyuboslavsky eae1fd30a1 Add stale issues workflow (#27047) ... Add stale issues workflow which: - marks `~engineering-initiated` issues with `stale` label and comment if they had no activity in the last 365 days (we have ~74 such issues right now) - closes `stale` issues after 14 days with no activity Examples of "recent" stale issues: - https://github.com/fleetdm/fleet/issues/13984 - https://github.com/fleetdm/fleet/issues/15571 - https://github.com/fleetdm/fleet/issues/16117 - https://github.com/fleetdm/fleet/issues/16352 Here's an example issue with a `stale` label. I ran the workflow and marked 27 issues as `stale` that had no activity for 1000 days. - https://github.com/fleetdm/fleet/issues/4631		2025-03-14 16:11:43 -05:00
..
actions/r2-upload	Keep all fleetd-base and fleetd-chrome artifacts. (#19749)	2024-06-17 15:49:06 -05:00
ISSUE_TEMPLATE	Air guitar process: add issue template & update process (#26808)	2025-03-13 11:07:10 -05:00
scripts	Update dogfood-policy-updater-latest-macos.sh (#26456)	2025-02-19 11:00:22 -06:00
workflows	Add stale issues workflow (#27047)	2025-03-14 16:11:43 -05:00
dependabot.yml	Remove daily schedule so it only gets triggered by security alerts (#14871)	2023-11-02 09:53:40 -05:00
pull_request_template.md	Update PR template with checklist item regarding potential load test impact of unreleased bug fixes (#26909)	2025-03-07 12:27:46 -06:00