chore: Add automation for stale issues and PRs#1927
Conversation
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
There was a problem hiding this comment.
Pull request overview
Adds a scheduled GitHub Actions workflow to automatically mark inactive PRs/issues as stale and close them after additional inactivity, using actions/stale with longer thresholds aligned to the referenced otel-java setup.
Changes:
- Introduce an hourly scheduled workflow to stale/close PRs after 120 + 30 days of inactivity.
- Introduce an hourly scheduled workflow to stale/close issues after 360 + 30 days of inactivity.
- Configure required job-level permissions for
actions/stale.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
I am once again unable to get linting to work locally to see what the issue is, and the CI output isnt helpful, i'll return to this later when i run |
Standalone example POMs don't inherit the spotless plugin from the project parent, so `spotless:apply` fails when they're in the reactor (JDK 25+ activates the examples-and-integration-tests profile). Use the fully-qualified plugin goal with profile deactivation to skip these modules. Add a `lint:example-poms` check to catch this class of issue in the future. Fixes #1927 Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
created #1931 for that |
|
CI lint failure is a Prettier formatting issue on the workflow YAML. Fix: (I know the CI output doesn't make this obvious — filed flint#89 to add a hint to the failure output.) |
## Summary - `mise run format` (i.e. `spotless:apply`) fails on JDK 25+ because standalone example POMs don't inherit the spotless plugin from the project parent, but are pulled into the reactor via the `examples-and-integration-tests` profile - Fix: use the fully-qualified plugin goal with profile deactivation - Add `lint:example-poms` check to catch this class of issue Relates #1927 (comment) ## Test plan - [x] `mise run format` succeeds - [x] `lint:example-poms` passes with the fix - [x] `lint:example-poms` fails when reverting the fix --------- Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
zeitlinger
left a comment
There was a problem hiding this comment.
LGTM! Clean setup, good separation of PR vs issue timelines. One minor thought: hourly cron (23 * * * *) seems frequent for a stale bot — daily (e.g. 23 6 * * *) would work just as well and save CI minutes. But not a blocker.
Heads up: lint CI is failing — please fix before merge.
Signed-off-by: Jay DeLuca <jaydeluca4@gmail.com>
Based on the automation used in the otel java projects, but with longer thresholds