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.
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
Adjust CI scripts for package specific tasks #139
Adjust CI scripts for package specific tasks #139
Changes from all commits
e934d90
12a7769
6703662
14e7cfb
eaff55b
ba39803
8a18ad6
9137bba
d6d6a03
644241a
3118b8a
d270d86
a795213
a80399e
720b86c
e153a5d
2c9e591
ca8c1c1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since linting just requires
pre-commit
actually we should probably make a newdeatched=True
Hatch environmentlint
for it that doesn't include all of the dev dependencies. This way we could just dohatch run lint:lint
on CI and it would be significantly faster. At the moment we install all the dependencies forall.py3.8
and then runpre-commit
that uses only one of those dependencies which is a bit silly.Not a big deal though, so feel free to do in a separate PR another time if you prefer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm good idea, let me see if I can incorporate that quickly still
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the other hand,
hatch run lint
is really used a lot, so would prefer not to havehatch run lint:lint
. Or do you mean to keeppre-commit
in the default environment as well?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's revisit in another PR if we still want to do changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maxschulz-COL yes, you're right - I originally put
lint
in thedefault
environment precisely so that we don't have to writehatch run lint:lint
. But probably the right way to do it is to make thehatch run lint:lint
the "correct" command with a detachedlint
environment and then put a script"lint" = ["hatch run lint:lint"]
in the default environment to just act as a shortcut so you can still dohatch run lint
.