Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(ci): add stale bot for issues #1002

Merged
merged 2 commits into from
Oct 22, 2024
Merged

chore(ci): add stale bot for issues #1002

merged 2 commits into from
Oct 22, 2024

Conversation

jakobmoellerdev
Copy link
Contributor

@jakobmoellerdev jakobmoellerdev commented Oct 22, 2024 •
edited by morri-son
Loading

What this PR does / why we need it

Adds a stale bot configuration

Which issue(s) this PR fixes

fix #285

fyi @morri-son

@github-actions github-actions bot added the chore label Oct 22, 2024
@hilmarf hilmarf added this to the 2024-Q4 milestone Oct 22, 2024
@morri-son
Copy link
Contributor

@jakobmoellerdev just fixes half of #285 . Is this enough for us and we don't need a rotten state?

@jakobmoellerdev
Copy link
Contributor Author

Discussed Async:

  1. We want 90 days stale interval
  2. we start with only stale and add rotten later if we need it

@jakobmoellerdev jakobmoellerdev marked this pull request as ready for review October 22, 2024 15:53
@jakobmoellerdev jakobmoellerdev requested a review from a team as a code owner October 22, 2024 15:53
morri-son
morri-son approved these changes Oct 22, 2024
View reviewed changes
Copy link
Contributor

@morri-son morri-son left a comment

Choose a reason for hiding this comment

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

lgtm

@jakobmoellerdev jakobmoellerdev enabled auto-merge (squash) October 22, 2024 18:51
@jakobmoellerdev jakobmoellerdev merged commit bb6ee63 into open-component-model:main Oct 22, 2024
15 checks passed
@hilmarf
Copy link
Member

hilmarf commented Oct 23, 2024

@jakobmoellerdev / @morri-son - should we move this action to our central place:
https://github.com/open-component-model/.github/tree/main/.github/workflows and then call(reuse) it from every repo, where we want to clean/mark issues automatically?

see sample usage: https://github.com/open-component-model/ocm-website/blob/main/.github/workflows/verify.yml#L11

@jakobmoellerdev
Copy link
Contributor Author

yes, great idea. I'll prepare a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@morri-son morri-son morri-son approved these changes

Assignees
No one assigned
Labels
chore
Projects
OCM Backlog Board
Status: 🍺 Done
Milestone
2024-Q4
Development

Successfully merging this pull request may close these issues.

Automatically set issue to / label with "stale" and "rotten" after some time
3 participants
@jakobmoellerdev @morri-son @hilmarf