-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove use of mode: all
#1122
Comments
I'd be fine with removing all the invocations in the repository but leaving the mode itself in case users want to use it in their own forks (it can be handy if you don't plan to make additional modes) |
wait, |
|
counterpoint: folks may want |
We talked about this on the maintenance session today.
|
#1122 We want to reduce the use of `mode:all` and instead have files that specifically target specific modes. This breaks up the existing sleep files to better capture their semantics and adds some comments. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
talonhub#1122 We want to reduce the use of `mode:all` and instead have files that specifically target specific modes. This breaks up the existing sleep files to better capture their semantics and adds some comments. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
talonhub#1122 We want to reduce the use of `mode:all` and instead have files that specifically target specific modes. This breaks up the existing sleep files to better capture their semantics and adds some comments. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Do we want to stop using
mode: all
? It seems like it could be surprising if a user creates a mode and unexpected commands are activeSee also #603
The text was updated successfully, but these errors were encountered: