Does not unmark when activity on PR when using keywords pulls: and issues:
See original GitHub issueIn this PR https://github.com/PowerShell/xSmbShare/pull/20#issuecomment-398221767 it did not remove the stale label ‘abandoned’ when there was activity on the PR (see style.yml). Looking at the code it seems is not using the `this.getConfigValue(type, ‘staleLabel’)’ or similar to get the correct value.
https://github.com/probot/stale/blob/628cbc9368f295b026da2e91d646ae1ed27cb136/index.js#L36-L37
@bkeepers Can I get your input on this one? Could this be the problem?
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
Using keywords in issues and pull requests - GitHub Docs
To mark an issue or pull request as a duplicate, type "Duplicate of" followed by the issue or pull request number it duplicates...
Read more >Microsoft VSTS Set Default Work Item State After Pull Request ...
No, it's designed for the PR is completed, that means the lined work items also completed. If the linked work items shoudn't closed...
Read more >Google Chrome Privacy Whitepaper
To turn off network predictions, uncheck “Preload pages for faster browsing and searching” in the “Privacy and security > Cookies” section of ...
Read more >Topics on Twitter - Twitter Help Center
We may also match you with other Topics that we think you are interested in based on your profile and activity, such as...
Read more >View, filter, and open pull requests - Azure Repos
To view PRs, you must be a member of the Azure DevOps project the PR is in, with Basic access or higher. If...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We’re seeing the same bug here: https://github.com/pydata/xarray/issues/2797. It’s happened on multiple issues.
I’m looking at the configurations between xarray and @infotexture to see if there’s some similarity. We both use the
stale
label, which is not default. Could that be a cause?Thanks for the awesome tool
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?