Pomax
Given the number of projects I already have commitments for, I'm already on negative time available. Happy to file a separate issue for that though, so it's its own thing.
v6.0.0 introduces "auth" at the client level, but this does not extend to clients that service multiple browsers. Which isn't even possible right now anyway so that's fine.
No it isn't: _issues need to have been triaged before they can go stale_. Instead the bot should be yelling at you, @github, for not even having looked at an...
Never have a bot mark an issue stale until it's been commented on by a project member. This isn't complicated.
And again. It's almost like no one's looking at this repo, eh @github?
Again: don't mark untriaged issues as stale. Ping the maintainers instead as "you have untriaged issues, review them"
@maxbeizer would you be the right person to ping on this? If not, is there someone else I can ping? It's been sitting around untriaged for a while now and...
@kivikakk yeah sorry about that, tagged the wrong person and immediately edited the post, but by then you got the notification already.
Thanks! The issue mentions three places though, was changing only two of them intentional?
(Or, alternatively, would it be possible to set up a windows release as a github action so that github just does that automatically and folks can just download the .exe...