Replies: 2 comments 1 reply
-
We actually already have these, implemented in #2509 |
Beta Was this translation helpful? Give feedback.
-
DescriptionI am having a bad experience as a user. I installed SuggestIf the filter in GitHub Actions is EvidenceThis is the execution for
The black output in my local is:
The problem in some extra comma which
-- https://github.com/airvzxf/tardis/actions/runs/8893046433/job/24418431698 black --check tardis
# Skipping .ipynb files as Jupyter dependencies are not installed.
# You can fix this by running ``pip install black[jupyter]``
# would reformat tardis/io/model/readers/blondin_toymodel.py |
Beta Was this translation helpful? Give feedback.
-
Validate and implement Linter before making a commit.
Description
I recommend that we implement and use Git Hooks (Atlassian and Geeks for Geeks), which allow us to validate and format the code when making a local commit, among many other things. Therefore, when we make a push to the server, it will already be validated and should pass the “code style / black (pull_request) workflow”. I implemented it a few years ago, and it was useful.
Proposal
I saw two ways to implement them, and I'll describe their pros and cons.
Types of Hooks:
Some other considerations, is that the academic or software developer needs to install
black
for any commit, but we can configure to detect if the changes were in the code (tardis folder) and apply only for them.Beta Was this translation helpful? Give feedback.
All reactions