Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Introduce install_command_post executed with --notest #1504

Open
webknjaz opened this issue Jan 18, 2020 · 1 comment
Open

Introduce install_command_post executed with --notest #1504

webknjaz opened this issue Jan 18, 2020 · 1 comment
Labels
feature:new something does not exist yet, but should help:wanted Issues that have been acknowledged, a solution determined and a PR might likely be accepted.

Comments

@webknjaz
Copy link
Contributor

So it's now quite popular to use tox --notest in CIs in a separate task/step to make it easier to distinguish between failing deps setup vs actual tests.

The concrete use-case I have in mind is running pre-commit install-hooks, that downloads hook repos and initializes virtualenvs for them, separately from pre-commit run.

pre-commit install-hooks should be executed with tox --notest while pre-commit run should go under commands.

This may or may not be a duplicate of #715, up to you.
@webknjaz webknjaz added the feature:new something does not exist yet, but should label Jan 18, 2020
@gaborbernat
Copy link
Member

My available efforts at the moment are aimed at fixing this as part of #1394, but that probably will take a while (ETA September). I think we can do it on top of that.

@webknjaz webknjaz mentioned this issue May 2, 2020
Merged
@gaborbernat gaborbernat added this to the 4.2 milestone Jan 13, 2022
@gaborbernat gaborbernat added the help:wanted Issues that have been acknowledged, a solution determined and a PR might likely be accepted. label Jan 13, 2022
@gaborbernat gaborbernat removed this from the P-2 milestone Jun 17, 2023
@webknjaz webknjaz moved this to 🦉 Inclusion ⚖️ in 📅 Procrastinating in public Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature:new something does not exist yet, but should help:wanted Issues that have been acknowledged, a solution determined and a PR might likely be accepted.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@webknjaz @gaborbernat