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.

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

adding templates #1062

Merged
merged 2 commits into from
May 30, 2024
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
5 changes: 5 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
blank_issues_enabled: false
contact_links:
- name: 💬 General Question
url: https://github.com/smithy-lang/smithy-kotlin/discussions/new/choose
about: Please ask and answer questions as a discussion thread
55 changes: 55 additions & 0 deletions .github/workflows/stale_issues.yaml
Copy link
Contributor

Choose a reason for hiding this comment

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

The file in our other repo is called stale_issue.yaml, is the file name important?

Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
name: "Close stale issues"

# Controls when the action will run.
on:
schedule:
- cron: "0 0/3 * * *"

jobs:
cleanup:
name: Stale issue job
runs-on: ubuntu-latest
steps:
- uses: aws-actions/stale-issue-cleanup@v4
with:
# Setting messages to an empty string will cause the automation to skip
# that category
ancient-issue-message: This is a very old issue that is probably not getting as much
attention as it deserves. We encourage you to check if this is still an issue in
the latest release and if you find that this is still a problem, please feel free
to provide a comment or open a new issue.
stale-issue-message: It looks like this issue has not been active for more than 5 days.
In the absence of more information, we will be closing this issue soon. If you find
that this is still a problem, please add a comment to prevent automatic closure, or
if the issue is already closed please feel free to reopen it.
stale-pr-message: It looks like this PR has not been active for more than five days. In
the absence of more information, we will be closing this PR soon. Please add a
comment to prevent automatic closure, or if the PR is already closed please feel
free to open a new one.

# These labels are required
stale-issue-label: closing-soon
exempt-issue-labels: no-auto-closure,feature-request
stale-pr-label: closing-soon
exempt-pr-labels: pr/needs-review
response-requested-label: response-requested

# Don't set closed-for-staleness label to skip closing very old issues
# regardless of label
closed-for-staleness-label: closed-for-staleness

# Issue timing
days-before-stale: 10
days-before-close: 4
days-before-ancient: 365

# If you don't want to mark a issue as being ancient based on a
# threshold of "upvotes", you can set this here. An "upvote" is
# the total number of +1, heart, hooray, and rocket reactions
# on an issue.
minimum-upvotes-to-exempt: 1

repo-token: ${{ secrets.GITHUB_TOKEN }}
loglevel: DEBUG
# Set dry-run to true to not perform label or close actions.
#dry-run: true
Loading