mirror of
https://github.com/hashicorp/packer.git
synced 2026-02-28 12:31:32 -05:00
cc5898022a
* chore: Set permissions for GitHub actions Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: neilnaveen <42328488+neilnaveen@users.noreply.github.com> * Update permissions for newly added actions * Remove deleted actions Co-authored-by: neilnaveen <42328488+neilnaveen@users.noreply.github.com>
35 lines
1.5 KiB
YAML
35 lines
1.5 KiB
YAML
name: 'Lock Threads'
|
|
|
|
on:
|
|
schedule:
|
|
- cron: '50 1 * * *'
|
|
|
|
# Only 50 issues will be handled during a given run.
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
lock:
|
|
permissions:
|
|
issues: write # for dessant/lock-threads to lock issues
|
|
pull-requests: write # for dessant/lock-threads to lock PRs
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: dessant/lock-threads@v3
|
|
with:
|
|
github-token: ${{ github.token }}
|
|
issue-comment: >
|
|
I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
|
|
|
|
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
|
|
issue-inactive-days: '30'
|
|
# Issues older than 180 days ago should be ignored
|
|
exclude-issue-created-before: '2020-11-01'
|
|
pr-comment: >
|
|
I'm going to lock this pull request because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
|
|
|
|
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
|
|
pr-inactive-days: '30'
|
|
# Issues older than 180 days ago should be ignored
|
|
exclude-pr-created-before: '2020-11-01'
|
|
|