Greg Hellings

If you have characters outside of Latin-1/CP1252 in your user path, then you might be encountering a known bug in Sword. Sword uses the standard C functions to open a...

You can add, as a pre-build event, `copy $(SolutionDir)\install.tar.gz $(SolutionDir)$(Platform)`, and the solution will do the needful during build.

@ajkavanagh For supporting both versions of tox, I am able to do it by leveraging import exceptions. The bulk of my code is the same, as it stems from the...

I just put in a PR to have Travis CI test. It could also do the builds, if there is need for that. I don't know if it has integration...

From the OASIS side of things, we need someone who is a SME in Satellite to spearhead that charge. I wrote the Satellite roll based off something an ops guy...

Hmm, I would rather not depend on a particular development tool to be present, such as git. I would prefer some sort of path exclusion option in the `tox.ini` [ansible]...

Actually, looking through the code, it already supports the option ```ini [ansible] ignore_path = foo bar/baz ``` Obviously if that's not feature-rich enough or needs to be improved we can...

Running Molecule tests was the original function of `tox-ansible`. If you need that functionality you'll need to use the tox 3.x series and tox-ansible 1.x series together. The 2.0 rewrite...

v1 had a `lint_all` target that ran yamllint, ansible-lint, and I think flake8, if memory serves correctly. It also provided a mechanism to pass command line arguments to each of...

This is of interest to me, as my system config flake uses keys named `nixstable` and `nixunstable` to bring in two versions of the packages to use on different systems...