Skip to content

Conversation

Parship999
Copy link
Contributor

@Parship999 Parship999 commented Jul 19, 2025

Which problem is this PR solving?

  • Fixes automated closing of stale pull requests and issues
  • The existing .github/stale.yml configuration was using the deprecated stale app which wasn't working. so it was removed

Description of the changes

  • issues stale after 90 days (only "question" labeled), PRs stale after 60 days
  • Add security hardening with step-security/harden-runner consistent with other workflows
  • schedule daily execution at 1:30 AM UTC with manual trigger support

How was this change tested?

  • The stale bot will automatically start working once merged to main branch
  • can be manually triggered from github actions tab for immediate testing

Checklist

Signed-off-by: Parship Chowdhury <i.am.parship@gmail.com>
@Parship999 Parship999 requested a review from a team as a code owner July 19, 2025 19:50
@Parship999 Parship999 requested a review from albertteoh July 19, 2025 19:50
@Parship999 Parship999 changed the title fixed githb stale bot configuration Fixes automated closing of stale pull requests and issues Jul 19, 2025
Signed-off-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
Signed-off-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
Signed-off-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
@yurishkuro yurishkuro changed the title Fixes automated closing of stale pull requests and issues Enable automated closing of stale pull requests and issues Jul 21, 2025
@yurishkuro yurishkuro merged commit b059cc6 into jaegertracing:main Jul 21, 2025
56 of 57 checks passed
on:
schedule:
# Run every Monday at 1:30 AM UTC
- cron: '30 1 * * 1'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cron expression 30 1 * * 1 is configured to run weekly on Mondays at 1:30 AM UTC, which doesn't match the PR description stating "schedule daily execution at 1:30 AM UTC". For daily execution, the cron expression should be 30 1 * * * instead.

Suggested change
- cron: '30 1 * * 1'
- cron: '30 1 * * *'

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

@yurishkuro
Copy link
Member

@Parship999 I did a test run, looks like it works. Please open another PR to remove the debug flag.

Copy link

codecov bot commented Jul 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.46%. Comparing base (d827d78) to head (b5541d9).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7347      +/-   ##
==========================================
- Coverage   96.49%   96.46%   -0.03%     
==========================================
  Files         378      378              
  Lines       22910    22999      +89     
==========================================
+ Hits        22107    22186      +79     
- Misses        608      615       +7     
- Partials      195      198       +3     
Flag Coverage Δ
badger_v1 9.10% <ø> (-0.07%) ⬇️
badger_v2 1.74% <ø> (-0.02%) ⬇️
cassandra-4.x-v1-manual 11.82% <ø> (-0.09%) ⬇️
cassandra-4.x-v2-auto 1.73% <ø> (-0.02%) ⬇️
cassandra-4.x-v2-manual 1.73% <ø> (-0.02%) ⬇️
cassandra-5.x-v1-manual 11.82% <ø> (-0.09%) ⬇️
cassandra-5.x-v2-auto 1.73% <ø> (-0.02%) ⬇️
cassandra-5.x-v2-manual 1.73% <ø> (-0.02%) ⬇️
elasticsearch-6.x-v1 16.61% <ø> (-0.14%) ⬇️
elasticsearch-7.x-v1 16.65% <ø> (-0.14%) ⬇️
elasticsearch-8.x-v1 16.80% <ø> (-0.16%) ⬇️
elasticsearch-8.x-v2 1.74% <ø> (-0.02%) ⬇️
grpc_v1 10.34% <ø> (-0.08%) ⬇️
grpc_v2 1.74% <ø> (-0.02%) ⬇️
kafka-3.x-v1 9.26% <ø> (-0.07%) ⬇️
kafka-3.x-v2 1.74% <ø> (-0.02%) ⬇️
memory_v2 1.74% <ø> (-0.02%) ⬇️
opensearch-1.x-v1 16.70% <ø> (-0.14%) ⬇️
opensearch-2.x-v1 16.70% <ø> (-0.14%) ⬇️
opensearch-2.x-v2 1.74% <ø> (-0.02%) ⬇️
query 1.74% <ø> (-0.02%) ⬇️
tailsampling-processor 0.48% <ø> (-0.01%) ⬇️
unittests 95.44% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Parship999 Parship999 mentioned this pull request Jul 21, 2025
github-merge-queue bot pushed a commit that referenced this pull request Jul 21, 2025
- continue from #7347

---------

Signed-off-by: Parship Chowdhury <i.am.parship@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants