Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions .github/workflows/close-inactive-issues.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
name: Close inactive issues and PRs
on:
schedule:
- cron: "30 1 * * *"
workflow_dispatch:
permissions: read-all
jobs:
close-issues:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9
with:
Copy link
Member

Choose a reason for hiding this comment

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

The messages imply that the Baremaps community provided a feedback and will do the actual work. What about encouraging ownership? See my suggestions below for the messages.

Copy link
Member Author

Choose a reason for hiding this comment

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

That sounds like a great idea.
In fact, the previous messages were from JUnit5, but the revised messages feel more encouraging. 💪🏻

Copy link
Member Author

Choose a reason for hiding this comment

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

Done in 273a92d !

Copy link
Member

Choose a reason for hiding this comment

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

Yes, I guess that JUnit does not need to build a community anymore 😆

only-labels: "status: waiting-for-feedback" # only consider issues and PRs with this label
Copy link
Member Author

Choose a reason for hiding this comment

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

This part checks for issues and PRs that are labeled with status: waiting-for-feedback.
So, we need to create the status: waiting-for-feedback label.

days-before-stale: 30 # 1 month
days-before-close: 60 # 2 months after being stale
stale-issue-label: "status: stale"
stale-pr-label: "status: stale"
Comment on lines +19 to +20
Copy link
Member Author

Choose a reason for hiding this comment

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

This part of the code checks issues and PRs in a stale state using this label.
Therefore, we should create the status: stale label.

stale-issue-message: >
If you would like us to be able to process this issue, please provide the requested information.
Copy link
Member

Choose a reason for hiding this comment

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

This issue has been inactive for a while. If you’re still interested, let us know how we can help! Our community is small, and we need contributors like you. If we don’t hear back, we may close it, but you’re always welcome to reopen it. Let’s build this together! 🚀

If the information is not provided within the next 2 months, we will be unable to proceed and this issue will be closed.
close-issue-message: >
Closing due to lack of requested feedback.
Copy link
Member

Choose a reason for hiding this comment

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

Closing this issue due to inactivity. If you’re still interested, let us know! Our community is small, and we need contributors like you. If you provide more details or take the lead on a solution, we’ll be happy to re-open it. Let’s build this together! 🚀

If you would like to proceed with your contribution, please provide the requested information and we will re-open this issue.
stale-pr-message: >
Copy link
Member

Choose a reason for hiding this comment

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

This PR has been inactive for a while. If you’re still working on it, let us know how we can help! Our community is small, and we need contributors like you. If we don’t hear back, we may close it, but you’re always welcome to reopen it. Let’s build this together! 🚀

If you would like us to be able to process this pull request, please provide the requested information or make the requested changes.
If the information is not provided or the requested changes are not made within the next 2 months, we will be unable to proceed and this pull request will be closed.
close-pr-message: >
Closing due to lack of requested feedback.
Copy link
Member

Choose a reason for hiding this comment

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

Closing this PR due to inactivity. If you’d like to continue, let us know! Our community is small, and we need contributors like you. Feel free to re-open this PR or submit a new one when you’re ready. Let’s build this together! 🚀

If you would like to proceed with your contribution, please provide the requested information or make the requested changes, and we will re-open this pull request.
30 changes: 30 additions & 0 deletions .github/workflows/label-opened-issues.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
name: Add label to opened issues
on:
issues:
types:
- opened
permissions: read-all
jobs:
label_issues:
runs-on: ubuntu-latest
permissions:
issues: write
steps:
- uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7
with:
script: |
const issue = await github.rest.issues.get({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
});
const originalLabels = issue.data.labels.map(l => l.name);
const statusLabels = originalLabels.filter(l => l.startsWith("status: "));
if (statusLabels.length === 0) {
github.rest.issues.addLabels({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
labels: ["status: new"]
Copy link
Member Author

Choose a reason for hiding this comment

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

This part of the workflow automatically applies the status: new label when a new issue is opened.
Therefore, we need to create the status: new label.

})
}
Loading