You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2023. It is now read-only.
It would be nice for when we are gearing up for close voting sessions focusing on tags to burninate. There is probably a SQL query that can return much better/more accurate results than the search query above.
Activated by saying "recent burninate requests" at Closey. It would respond with Closey taking the tag from the title (usually the tag is mentioned in the first instance of square brackets [ ] in the question title) and using it as the link text (i.e. magazine, placement, router)
The text was updated successfully, but these errors were encountered:
I don't see why this should be the most recent tags. We actually want to finish burnination efforts, don't we?
I think if we just grab from the rss feed we can find the recent tags that are not status-completed and not negatively scored, and use those to decide what to work on. Top three voting out of 20 most recent posts might be a good start.
Update: due to "we want to get version 2 out the door", this will not be a feature in version 2.0. However, this feature still has merit and will still be considered.
Pulled from this URL here: http://meta.stackoverflow.com/search?tab=newest&q=[burninate-request]%20score%3a0..%20is%3aquestion
It would be nice for when we are gearing up for close voting sessions focusing on tags to burninate. There is probably a SQL query that can return much better/more accurate results than the search query above.
Activated by saying "recent burninate requests" at Closey. It would respond with Closey taking the tag from the title (usually the tag is mentioned in the first instance of square brackets [ ] in the question title) and using it as the link text (i.e. magazine, placement, router)
The text was updated successfully, but these errors were encountered: