Comments (4)
In the linked case, you could exempt the "security" label. Problem solved.
from stale.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
from stale.
@Be-ing the point is we still want to be reminded of old issues, but the time between two reminders should be proportional to the age of the issue. In other words, we want to be reminded more frequently of recent issues and less frequently of older issues.
This is because the bot doesn't understand the issues and the users don't tell the bot whether a particular issue is expected to get fixed within the week or within the next two years, which varies from one issue to another. So, when a user tells the bot "don't close this yet" it constitutes feedback that means roughly "please double the time until you can bug me again". It doesn't have to double, it could be 1.5 or any constant factor. Assuming a factor 2 for the sake of simplicity, this gives us the following schedule:
- t0 + 1 month
- t0 + 2 months
- t0 + 4 months
- t0 + 8 months
- t0 + 16 months
where t0 is when the issue was created. With this schedule, we'd get 4 reminders within the first year rather than 12, and I think it would be much nicer.
from stale.
Even worse, even if I’m annoyed by the behavior, I cannot just “fork my own”, because I still need to persuade all the maintainers to use my fork before I can avoid such naggings.
from stale.
Related Issues (20)
- Eser4444 HOT 1
- How to run for other repos in the same organization HOT 3
- Feature request: Option to move a PR from "open" to "draft" HOT 2
- Stale workflow fails to override cache. HOT 4
- Stale label not removed after receiving comments/commit HOT 5
- Error delete _state: [403] Resource not accessible by integration HOT 8
- Stale issues are not getting closed HOT 5
- State restoration fails if a repo has many caches HOT 3
- Have one workflow ignore the state saved by another HOT 3
- [wishlist
- [wishlist] mark previous comment(s) as outdated when removing 'stale' label HOT 1
- Allow filtering of PRs by review status or other criteria HOT 2
- Support markdown comments HOT 1
- Action is not working and is always erroring out HOT 3
- Actions fails if rate Limit is not enabled HOT 2
- `actions: write` is too permissive HOT 1
- Feature request: Close draft PRs only HOT 1
- Github actions workflow issue for long running jobs - Not able to view Logs & status marked as cancelled but overall workflow seems to be running HOT 4
- Error when removing the label: "Label does not exist" HOT 2
- Remove Stale Branches HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stale.