Features/integrate GitHub actions ci cd linters #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This enables users to have inline comments in deps lines in `tox.ini`. In particular, this allows having pyup bot integration. Ref: pyupio/dparse#34 Ref: ansible/molecule#1973 Fixes tox-dev#1260
release 3.9.0
tox ignores unknown CLI arguments when provisioning is on and outside of the provisioned environment (allowing provisioning arguments to be forwarded freely)
… listed default environment variables, these show up under extra (tox-dev#1284)
> Black, your uncompromising #Python code formatter, was a project > created with the community in mind from Day 1. Today we moved it under > the PSF umbrella. It's now available on GitHub under > https://github.com/python/black/ . You install and use it just like > before. https://twitter.com/llanga/status/1123980466292445190
* move to improved Azure template * add architecture support, log discovery * fix * fix * fix * debug
release 3.10.0
…on and package versions (tox-dev#1298) and package versions
release 3.11.0
…ualenvs (tox-dev#1301) * Fixed result of tox_get_python_executable not being used to make virtualenvs * fix formatting and add changelog
release 3.11.1
…x-dev#1311) * Adding TOX_PARALLEL_NO_SPINNER to disable spinner for CI tools. * Adding unit tests for TOX_PARALLEL_NO_SPINNER env var. * Updating CONTRIBUTORS and changelog for TOX_PARALLEL_NO_SPINNER env var.
* pep-514 implementation * reorganize interpreter * report failures * report failures
* Correct ``--result-json`` output with ``--parallel``. (tox-dev#1295) When using ``--parallel`` with ``--result-json`` the test results are now included the same way as with serial runs. This is accomplished by generating json result output for each individual run and at the end copy the data into the main json result output. * avoid duplication in code, improve coverage
release 3.13.1
* Add explicit check for pypy venv * Add changelog entry * Add regression test for --recreate
release 3.13.2
* Fix repo file links in the PR template * Add a misc changelog fragment
…#1366) `depends` and `parallel_show_output` are not global settings, they're per-environment settings. I think they got listed in the global settings section by accident.
…dev#1368) * Use importlib.metadata from the standard library on Python 3.8+ Fixes tox-dev#1367 * Azure Pipelines: Add Python 3.8
* Make changelog instructions visible @ folder view * Add a change fragment
…#1399) * clarify behaviour if recreate is set to false in config.rst (tox-dev#1372) * added file to changelog (tox-dev#1372) * add new line at the end of changelog entry (tox-dev#1372)
As identified by Debian's lintian: - comand -> command - suceeds -> succeeds - intepreter -> interpreter - allow(s) to -> allow(s) you/one to
webknjaz
force-pushed
the
features/integrate-github-actions-ci-cd--linters
branch
from
18b453c to
7faa411
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks for contributing a pull request!
If you are contributing for the first time or provide a trivial fix don't worry too
much about the checklist - we will help you get started.
Contribution checklist:
(also see CONTRIBUTING.rst for details)
in message body
<issue number>.<type>.rstfor example (588.bugfix.rst)<type>is must be one ofbugfix,feature,deprecation,breaking,doc,miscsuperuser."CONTRIBUTORS(preserving alphabetical order)