From a0aaccebc679fab136a7a50eed3664a61e6d1d78 Mon Sep 17 00:00:00 2001 From: Andreas Thaler Date: Tue, 23 Jan 2024 13:40:51 +0100 Subject: [PATCH] chore: Switch to stale bot --- .github/ISSUE_TEMPLATE/bug-report.md | 6 ++ .github/ISSUE_TEMPLATE/decision-record.md | 35 -------- .../documentation-improvement.md | 34 -------- .github/ISSUE_TEMPLATE/feature-request.md | 6 ++ .../ISSUE_TEMPLATE/new-sig-or-wg-proposal.md | 80 ------------------- .../ISSUE_TEMPLATE/security-vulnerability.md | 57 ------------- .github/OWNERS | 7 -- .github/issue-template.md | 8 -- .github/stale.yml | 19 ----- .github/workflows/periodic-github-checks.yaml | 31 +++++++ ...ull-code-checks.yml => pr-code-checks.yml} | 0 ...ull-docu-checks.yml => pr-docu-checks.yml} | 0 ...github-checks.yml => pr-github-checks.yml} | 0 13 files changed, 43 insertions(+), 240 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/decision-record.md delete mode 100644 .github/ISSUE_TEMPLATE/documentation-improvement.md delete mode 100644 .github/ISSUE_TEMPLATE/new-sig-or-wg-proposal.md delete mode 100644 .github/ISSUE_TEMPLATE/security-vulnerability.md delete mode 100644 .github/OWNERS delete mode 100644 .github/issue-template.md delete mode 100644 .github/stale.yml create mode 100644 .github/workflows/periodic-github-checks.yaml rename .github/workflows/{pull-code-checks.yml => pr-code-checks.yml} (100%) rename .github/workflows/{pull-docu-checks.yml => pr-docu-checks.yml} (100%) rename .github/workflows/{pull-github-checks.yml => pr-github-checks.yml} (100%) diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md index 5360ddf..1bcfd40 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.md +++ b/.github/ISSUE_TEMPLATE/bug-report.md @@ -30,3 +30,9 @@ Describe where it appears, when it occurred, and what it affects. --> **Troubleshooting** + +**Release Notes** + +``` + +``` diff --git a/.github/ISSUE_TEMPLATE/decision-record.md b/.github/ISSUE_TEMPLATE/decision-record.md deleted file mode 100644 index bb997a1..0000000 --- a/.github/ISSUE_TEMPLATE/decision-record.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -name: Decision record -about: Decision record ---- - - -Created on {YYYY-MM-DD} by {name and surname (@Github username)}. - -## Decision log - -| Name | Description | -|-----------------------|------------------------------------------------------------------------------------| -| Title | {Provide a brief summary of the decision.} | -| Due date | {Specify the date by which the SIG or WG members need to make the decision. Use the `YYYY-MM-DD` date format.} | -| Status | {The status of the document can be `Accepted`, `Declined`, or `Proposed` when it is waiting for a decision. This section should contain one of these three words followed by the date on which the status of the document is agreed on. Follow the `YYYY-MM-DD` format for the date. For example, write `Proposed on 2018-03-20` or `Accepted on 2018-03-23`. Add the new status when it changes. Do not overwrite previous status entries.}| -| Decision type | {Type in `Binary`, `Choice`, or `Prioritization`. The `Binary` type refers to the yes/no decisions, the `Choice` type means that the decision involves choosing between many possibilities, such as a name for a new product, and the `Prioritization` type involves ranking a number of options, such as choosing the next five features to build out of one hundred possible options.} | -| Affected decisions | {Specify the ID of the decision issue or a link to the previous decision record which is affected by this decision. Use the `#{issueid}\|{decision-record-URL}(replaces\|extends\|depends on)` format. For example, write `#265(replaces)` or `#278(depends on)` which means that the decision you propose replaces the issue 265 or depends on the issue 278. Specify as many references as possible and separate them with a comma. Write `None` if no other decision is affected.}| - -## Context - - - -## Decision - - - -## Consequences - - diff --git a/.github/ISSUE_TEMPLATE/documentation-improvement.md b/.github/ISSUE_TEMPLATE/documentation-improvement.md deleted file mode 100644 index 9fbb8a2..0000000 --- a/.github/ISSUE_TEMPLATE/documentation-improvement.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -name: Documentation improvement -about: Suggest an improvement or report a bug in the documentation ---- - - - -**Description** - - - -**Area** - - - -**Reasons** - - - -**Assignees** - -@kyma-project/technical-writers - -**Attachments** - - \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md index 8040e55..be3ddf9 100644 --- a/.github/ISSUE_TEMPLATE/feature-request.md +++ b/.github/ISSUE_TEMPLATE/feature-request.md @@ -19,3 +19,9 @@ about: Suggest an improvement to the project **Attachments** + +**Release Notes** + +``` + +``` diff --git a/.github/ISSUE_TEMPLATE/new-sig-or-wg-proposal.md b/.github/ISSUE_TEMPLATE/new-sig-or-wg-proposal.md deleted file mode 100644 index 9c62616..0000000 --- a/.github/ISSUE_TEMPLATE/new-sig-or-wg-proposal.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -name: SIG or WG proposal -about: Propose a new SIG or WG ---- - - - -**Proposal type** - -* Special Interest Group (SIG) -* Working Group (WG) - -**Name** -* Full name of the group: - -* Abbreviated name: - -**Earliest start date** - -* {YYYY-MM-DD} - -**Visibility** - -* Internal -* Public - -**Keywords** (optional) - -* ... -* ... -* ... - -**Proposers** - -* ... -* ... -* ... - -**Purpose and goals** - - -**Benefits** - - -**Expected results** - - -**Expected membership and governance** - -* Meeting frequency: -* Membership: -* Duration: - -**Previous approach** (optional) - - -**Measures of success** (optional for SIG) - -* ... -* ... -* ... - -**Assessment frequency** - -* Monthly -* Quarterly -* Biannually -* Annually - -**Exit criteria** - -* ... -* ... -* ... diff --git a/.github/ISSUE_TEMPLATE/security-vulnerability.md b/.github/ISSUE_TEMPLATE/security-vulnerability.md deleted file mode 100644 index b3d422e..0000000 --- a/.github/ISSUE_TEMPLATE/security-vulnerability.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -name: Security vulnerability -about: Report vulnerability in the project ---- - - - -**Description** - - - - - -**Steps to exploit** - - - -**Risk assessment** - - -[{CVSS Vector String}]({CVSS Calculator URL}) **{CVSS Base Score} ({CVSS Base Severity})** - - - - - -**Proposed mitigation** - - diff --git a/.github/OWNERS b/.github/OWNERS deleted file mode 100644 index 42295db..0000000 --- a/.github/OWNERS +++ /dev/null @@ -1,7 +0,0 @@ -reviewers: - - ci-reviewers -approvers: - - ci-approvers - -labels: - - area/ci diff --git a/.github/issue-template.md b/.github/issue-template.md deleted file mode 100644 index 9032a0e..0000000 --- a/.github/issue-template.md +++ /dev/null @@ -1,8 +0,0 @@ - - -**Description** - - diff --git a/.github/stale.yml b/.github/stale.yml deleted file mode 100644 index b70d9ba..0000000 --- a/.github/stale.yml +++ /dev/null @@ -1,19 +0,0 @@ -# Number of days of inactivity before an issue becomes stale -daysUntilStale: 60 -# Number of days of inactivity before a stale issue is closed -daysUntilClose: 7 -# Label to use when marking an issue as stale -staleLabel: lifecycle/stale -# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable -exemptLabels: - - lifecycle/frozen - - lifecycle/active -# Comment to post when marking an issue as stale. Set to `false` to disable -markComment: | - This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. - Thank you for your contributions. -# Comment to post when closing a stale issue. Set to `false` to disable -closeComment: | - This issue has been automatically closed due to the lack of recent activity. - /lifecycle rotten - diff --git a/.github/workflows/periodic-github-checks.yaml b/.github/workflows/periodic-github-checks.yaml new file mode 100644 index 0000000..f74f1e4 --- /dev/null +++ b/.github/workflows/periodic-github-checks.yaml @@ -0,0 +1,31 @@ +name: 'Periodic Github Checks' + +on: + schedule: + - cron: '0 0 * * *' # Runs daily at midnight + workflow_dispatch: # Allows manual triggering of the workflow + +jobs: + stale-issues: + runs-on: ubuntu-latest + steps: + - uses: actions/stale@v9 + with: + days-before-stale: 60 + days-before-close: 7 + stale-issue-label: 'lifecycle/stale' + stale-pr-label: 'lifecycle/stale' + exempt-issue-labels: 'lifecycle/frozen' + exempt-pr-labels: 'lifecycle/frozen' + stale-issue-message: | + This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. + Thank you for your contributions. + stale-pr-message: | + This pull request has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. + Thank you for your contributions. + close-issue-message: | + This issue has been automatically closed due to the lack of recent activity. + /lifecycle rotten + close-pr-message: | + This pull request has been automatically closed due to the lack of recent activity. + /lifecycle rotten diff --git a/.github/workflows/pull-code-checks.yml b/.github/workflows/pr-code-checks.yml similarity index 100% rename from .github/workflows/pull-code-checks.yml rename to .github/workflows/pr-code-checks.yml diff --git a/.github/workflows/pull-docu-checks.yml b/.github/workflows/pr-docu-checks.yml similarity index 100% rename from .github/workflows/pull-docu-checks.yml rename to .github/workflows/pr-docu-checks.yml diff --git a/.github/workflows/pull-github-checks.yml b/.github/workflows/pr-github-checks.yml similarity index 100% rename from .github/workflows/pull-github-checks.yml rename to .github/workflows/pr-github-checks.yml