You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bc...@apache.org on 2021/04/03 15:38:44 UTC
[trafficserver] branch bryancall-patch-2 created (now d4e9ca1)
This is an automated email from the ASF dual-hosted git repository.
bcall pushed a change to branch bryancall-patch-2
in repository https://gitbox.apache.org/repos/asf/trafficserver.git.
at d4e9ca1 Automatically marks PRs and issues stale
This branch includes the following new commits:
new d4e9ca1 Automatically marks PRs and issues stale
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[trafficserver] 01/01: Automatically marks PRs and issues stale
Posted by bc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
bcall pushed a commit to branch bryancall-patch-2
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
commit d4e9ca1abf9e71999af5f5cd3272f0771fdc25e2
Author: Bryan Call <bc...@apache.org>
AuthorDate: Sat Apr 3 08:38:28 2021 -0700
Automatically marks PRs and issues stale
Marks PRs and issues with the Stale tag and makes a comment on the PR and issue.
---
.github/workflows/stale.yml | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
new file mode 100644
index 0000000..9cf41c1
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,24 @@
+name: Mark stale issues and pull requests
+
+on:
+ schedule:
+ - cron: "30 1 * * *"
+
+jobs:
+ stale:
+
+ runs-on: ubuntu-latest
+
+ steps:
+ - uses: actions/stale@v3
+ with:
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
+ stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.'
+ stale-pr-message: 'This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.'
+ stale-issue-label: 'Stale'
+ stale-pr-label: 'Stale'
+ days-before-pr-stale: 90
+ days-before-issue-stale: 365
+ days-before-pr-close: -1
+ days-before-issue-close: -1
+ debug-only: true