-
-
Notifications
You must be signed in to change notification settings - Fork 478
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
[Feature Request] Check-only mode for CI #188
Comments
I think as a potential workaround, you could use the new |
Yes, I'm currently doing sth like that... just need #189 to be addressed for that workaround to fully work :/ |
If you want to run doctoc in the CI, ensuring tocs are up-to-date or fail the job if not, I highly suggest you this: https://github.com/fluidattacks/makes#formatmarkdown This is how a CI failure looks like: fluidattacks/makes#190 (comment) It can also be executed locally, which is nice |
Thanks @kamadorueda, that seems like a neat case for using nix. I'd say the vast majority of people don't use it, though, so I think there's still a use case for developing something like this. |
The more native the better! I agree with you |
A |
Sorry if it's a duplicate... an option that would just check if the ToCs are up-to-date without modifying anything would be useful for the CI use.
Currently I need to do sth like that:
https://github.com/VirtusLab/git-machete-intellij-plugin/pull/636/files#diff-78a8a19706dbd2a4425dd72bdab0502ed7a2cef16365ab7030a5a0588927bf47R14
The text was updated successfully, but these errors were encountered: