[cross-]referenced as reason for non-staleness? about stale HOT 10 CLOSED

Interesting. I think that's a great idea.

Related: https://github.com/clarkbw/probot-in-progress @clarkbw

GitHub

clarkbw/probot-in-progress

probot-in-progress - A Probot that marks issues with a specific label when an in progress PR indicates they will be fixed

from stale.

Is this still relevant? If so, please comment with any updates or addition details.

from stale.

Thank you stale bot I guess you are serving your purpose, made me visit.

I see looking at the query built by stalebot and https://help.github.com/articles/searching-issues-and-pull-requests/ why https://github.com/clarkbw/probot-in-progress is so relevant -- there isn't a query operator for references, so to get at them, we'd need code similar to probot-in-progress that looks for references in other issues/pulls.

~3 ways to implement in stalebot, if I understand:

1. Add (or not if desired as default) something like an exemptReferenced configuration parameter, if that's turned on or default either
   1. use probot-in-progress like code added to stalebot to unstale issues when referenced; seems not ideal because a referenced issue maybe should not be marked stale in the first place
   2. or do some post-filtering of query to eliminate issues that have been referenced (I don't know offhand how to do this but imagine it can't be that hard)
2. Just document that one can set exemptLabels to include the ones populated by probot-in-progress and also install probot-in-progress if one does not want stalebot to mark issues that there's some evidence someone is working on as stale.

I suppose which is "right" depends in part on whether probots are typically kitchen sink or expected to do as little as possible and rely on other probots also doing very little to achieve something.

Searching issues and pull requests - User Documentation

You can search for issues and pull requests using these search qualifiers in any combination. …

GitHub

clarkbw/probot-in-progress

probot-in-progress - A Probot that marks issues with a specific label when an in progress PR indicates they will be fixed

from stale.

Is this still relevant? If so, please comment with any updates or addition details.

from stale.

Will this feature be implemented after all?

from stale.

The documentation-only-work-with-probot-in-progress implementation above would be easiest. Is probot-in-progress going to be available from https://probot.github.io/apps/ at some point @clarkbw?

Probot

Featured Apps

GitHub Apps to automate and improve your workflow

from stale.

some point @clarkbw?

I don't think I have the time. 😢

from stale.

…or do some post-filtering of query to eliminate issues that have been referenced (I don't know offhand how to do this but imagine it can't be that hard)

Right now stale relies heavily on GitHub search. If the notion of referenced could be added to search, it'd be really easy. I suspect though what you really want to know is if there is an open pull request that references this issue. That gets a little more complicated.

It'll likely mean an n+1 query for every open issue to see if there's a PR that references it.

I'm not opposed to adding this feature, but it'll likely require a bit of work. I'm happy to give feedback if anyone wants to attempt it.

from stale.

FYI, I had hoped to tackle the fundamental API issue this year. But don’t let my optimism there deter you from getting anything done.

from stale.

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

from stale.