Add pre-commits with lint checks #3398

Open
opened 2020-08-30 15:14:54 +00:00 by jaraco · 3 comments

CI includes "code checks" including flake8 checks. It's common for a developer to make changes, test, commit, then push only to find that linter checks fail. To avoid this unwelcoming workflow, the team would like to declare pre-commit hooks that a developer could run to avoid committing code that will fail code checks (at least flake8).

CI includes "code checks" including flake8 checks. It's common for a developer to make changes, test, commit, then push only to find that linter checks fail. To avoid this unwelcoming workflow, the team would like to declare pre-commit hooks that a developer could run to avoid committing code that will fail code checks (at least flake8).
jaraco added the
unknown
normal
enhancement
n/a
labels 2020-08-30 15:14:54 +00:00
jaraco added this to the Support Python 3 milestone 2020-08-30 15:14:54 +00:00
jaraco self-assigned this 2020-08-30 15:48:52 +00:00
Author

PR: https://github.com/tahoe-lafs/tahoe-lafs/pull/798

It's failing due to flaky tests.

PR: <https://github.com/tahoe-lafs/tahoe-lafs/pull/798> It's failing due to flaky tests.

Here's another PR that runs the full test suite before allowing a push and includes setting up the hook in the local checkout into the ./Makefile.

Here's [another PR](https://github.com/tahoe-lafs/tahoe-lafs/pull/830) that runs the full test suite before allowing a push and includes setting up the hook in the local checkout into the `./Makefile`.

Ticket retargeted after milestone closed

Ticket retargeted after milestone closed
itamarst removed this from the Support Python 3 milestone 2023-09-05 14:20:22 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#3398
No description provided.