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

Issues being closed despite setting days-before-close to -1 #44

Closed
astrogeco opened this issue Apr 14, 2020 · 1 comment
Closed

Issues being closed despite setting days-before-close to -1 #44

astrogeco opened this issue Apr 14, 2020 · 1 comment

Comments

@astrogeco
Copy link

astrogeco commented Apr 14, 2020

I tried running the code below on a test repository. The issues get tagged appropriately but then they get closed despite using the days-before-close: -1 flag.

Steps to reproduce:

  1. Create new repository
  2. Add script below to .github/workflows
  3. Open a couple of test issues
  4. Wait for workflow to run
name: Mark stale issues and pull requests

on:
  schedule:
  - cron: "10 * * * *"

jobs:
  stale:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/stale@v1
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        stale-issue-message: 'This issue has not been updated in the last TBD days'
        stale-pr-message: 'This PR has not been updated in the last TBD days'
        stale-issue-label: 'stale'
        stale-pr-label: 'stale'
        days-before-stale: 0
        days-before-close: -1
@hross
Copy link
Contributor

hross commented Apr 16, 2020

You will need to update to the latest release here: https://github.com/actions/stale/releases/tag/v2.0.0

The action you are referencing is using stale@v1 and you want stale@v2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants