Implement target in Makefile to run github CI-like checks locally #1753
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Implement target in Makefile to run github CI-like checks locally.
What is the current behavior?
Currently there is no fast & easy way to run tests & checks before commit locally.
What is the new behavior (if this is a feature change)?
Command
make testsruns the same tests & checks as github CI jobs for pull-request but locally.Other information:
I understand the irony that the whole point of CI philosophy is to use "big" & "fast" infrastructure to test code instead of small & slow local PCs. But for someone like me this should help to reduce a bit those awkward embarrassing moments when PR turns red only because I forgot tab in python script or some quotes in shell script. 😳