Code Monkey home page Code Monkey logo

Comments (9)

mosabua avatar mosabua commented on August 27, 2024 2

I am trying this out @shmishra99 .. I think it would be great to have this in the docs .. you want me to send a PR to add it once I confirmed it works?

days-before-issue-stale: -1
day-before-issue-closed: -1

I assume the same approach works for excluding PRs:

days-before-pr-stale: -1
day-before-pr-closed: -1

from stale.

shmishra99 avatar shmishra99 commented on August 27, 2024 1

@alper
To opt out of the stale issue management for all issues, configure days-before-issue-stale and day-before-issue-closed` with a value of -1.

from stale.

marko-zivic-93 avatar marko-zivic-93 commented on August 27, 2024

Hello @alper
Thank you for filing your issue. We will take a look and come back to you as soon as possible.

from stale.

dsame avatar dsame commented on August 27, 2024

Hello alper, most of the operations have -pr- variant - they affect only PR's according to the documentation. Can you please clarify what namely operation do you want to be applied?

from stale.

alper avatar alper commented on August 27, 2024

I couldn't figure out how to not have it work on issues so I set the issue days to 999.

That should probably work long enough for my purposes.

from stale.

dsame avatar dsame commented on August 27, 2024

Hello @alper , the provided info is not enough to identify the exact problem, but generally you should use only -pr- and do not use -issue- variants of the configuration option in order to process only PRs.

Did it help?

from stale.

joaopgrassi avatar joaopgrassi commented on August 27, 2024

Hello alper, most of the operations have -pr- variant - they affect only PR's according to the documentation. Can you please clarify what namely operation do you want to be applied?

This does not work. I have set up only the *-pr variant of configuration, but the bot still runs on issues because it there are defaults for days-before-stale: 60 and days-before-close: 7.

You can see this in this example Action run: https://github.com/open-telemetry/semantic-conventions/actions/runs/7925571995/job/21638954263

Run actions/stale@v9
  with:
    repo-token: ***
    stale-pr-message: This PR was marked stale due to lack of activity. It will be closed in 7 days.
    close-pr-message: Closed as inactive. Feel free to reopen if this PR is still being worked on.
    exempt-pr-labels: bug,work in progress,experts needed
    exempt-draft-pr: true
    days-before-pr-stale: 15
    days-before-pr-close: 7
    days-before-stale: 60 <<<<<<<<<<<<<<<<<< I did not add this in my config
    days-before-close: 7 <<<<<<<<<<<<<<<<<< I did not add this in my config
    stale-issue-label: Stale
    close-issue-reason: not_planned
    stale-pr-label: Stale
    exempt-all-milestones: false
    operations-per-run: 30
    remove-stale-when-updated: true
    debug-only: false
    ascending: false
    delete-branch: false
    exempt-all-assignees: false
    enable-statistics: true
    ignore-updates: false
    include-only-assigned: false

My current config is:

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v9
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          stale-pr-message: 'This PR was marked stale due to lack of activity. It will be closed in 7 days.'
          close-pr-message: 'Closed as inactive. Feel free to reopen if this PR is still being worked on.'
          exempt-pr-labels: 'bug,work in progress,experts needed'
          exempt-draft-pr: true
          days-before-pr-stale: 15
          days-before-pr-close: 7

from stale.

Gustry avatar Gustry commented on August 27, 2024

It seems I can confirm the behavior just above. I used only the *-pr-* configuration, but reading the logs, it's also checking issues :

[#4349] Issue #4349
  [#4349] Found this issue last updated at: 2024-05-21T08:26:23Z
....
 Processed items: 40
├── Processed issues: 31
└── Processed PRs   : 9

from stale.

DjoykeAbyah avatar DjoykeAbyah commented on August 27, 2024

Hi @dsame!

I'm experiencing the same issue but the other way around. I've tried to override with a 'do not stale' label but it ignores it. I also tried setting up only the *-issues variant of configuration and it does not work, also for setting the *-pr to -1.
Could an if statement maybe solve this issue?

regards,

Djoyke

from stale.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.