tahoe-lafs/.pre-commit-config.yaml

repos:
  - repo: "local"
    hooks:
    - id: "codechecks"
      name: "codechecks"
      stages: ["push"]
      language: "system"
      files: ".py$"
      entry: "tox -e codechecks"
      pass_filenames: true
test(vcs): Add a VCS push hook to run tests Personally, I can't stand working without a VCS hook anymore. It saves me so much time in context switches from revisiting and revising PRs when I see that the CI run is red. Much better to fail before I push so I can revise while the relevant changes are fresh in my head. In order to start using this, one has to run `$ make build` first. Should I add that and make other documentation changes in the wiki related to my changes in this PR? 2020-09-25 17:04:10 +00:00			`repos:`
Only run codechecks on changed Python source files 2020-11-19 16:12:08 +00:00			`- repo: "local"`
test(vcs): Add a VCS push hook to run tests Personally, I can't stand working without a VCS hook anymore. It saves me so much time in context switches from revisiting and revising PRs when I see that the CI run is red. Much better to fail before I push so I can revise while the relevant changes are fresh in my head. In order to start using this, one has to run `$ make build` first. Should I add that and make other documentation changes in the wiki related to my changes in this PR? 2020-09-25 17:04:10 +00:00			`hooks:`
Only run codechecks on changed Python source files 2020-11-19 16:12:08 +00:00			`- id: "codechecks"`
			`name: "codechecks"`
test(vcs): Add a VCS commit hook to run linters 2020-09-27 16:30:06 +00:00			`stages: ["push"]`
Only run codechecks on changed Python source files 2020-11-19 16:12:08 +00:00			`language: "system"`
			`files: ".py$"`
Just do codechecks pre-push 2020-10-23 18:52:45 +00:00			`entry: "tox -e codechecks"`
Only run codechecks on changed Python source files 2020-11-19 16:12:08 +00:00			`pass_filenames: true`