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: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>
27 lines
895 B
YAML
27 lines
895 B
YAML
# https://github.com/marketplace/actions/close-stale-issues
|
|
# https://github.com/actions/stale/blob/master/action.yml
|
|
# https://github.com/actions/stale
|
|
name: Mark stale issues and pull requests
|
|
on:
|
|
schedule:
|
|
- cron: "0 0 * * *"
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
stale:
|
|
permissions:
|
|
issues: write # for actions/stale to close stale issues
|
|
pull-requests: write # for actions/stale to close stale PRs
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/stale@v5
|
|
with:
|
|
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
# stale-issue-message: 'Stale issue message'
|
|
# stale-issue-label: 'no-issue-activity'
|
|
stale-pr-message: 'This pull request seems to be stale. Are you still planning to work on it? We will automatically close it in 30 days.'
|
|
stale-pr-label: 'stale'
|
|
days-before-stale: 30
|
|
days-before-close: 30
|