- Open the directory you'd like to put the clone's directory into in a terminal window.
- Clone the wiki, which will create the autokey.wiki directory inside of the current directory:
git clone https://github.com/autokey/autokey.wiki.git
π Caution: Although the steps below have you creating and using a clone of AutoKey, the clone shares the same configuration folder as the installed copy of AutoKey. Since there's always a risk of corruption of files when one is testing new code, it's best not to run these tests on a system where the installed copy of AutoKey contains valued custom phrases and/or scripts. I recommend creating a virtual machine instead.
- Make sure that the system you'll be doing the tests on already has a working copy of AutoKey installed on it (so that you'll already have all the necessary apt dependencies).
- Install the git package in Kubuntu.
- Install the tox package in Kubuntu.
- Open the directory you'd like to create the cloned autokey directory inside of in a terminal window.
- Clone the PR:
- Open the
.github/workflows
directory. - Check the action versions:
- Check the `build.yml`_ file:
The testing methods below can be done inside of a terminal window on a machine that has AutoKey already installed on it (in fact, that's recommended since it will likely provide you with all of the necessary dependencies in advance).
π π π π π π
It's important to note that lthough each instance of AutoKey will be independent, the AutoKey configuration from your installed copy of AutoKey will be used, which means all of these tests will have full access to your phrases and scripts and changes you make to those while testing will affect your installed version of AutoKey as well.
π π π π π π
We don't have a tox.ini
file and it may be necessary. From what I've been able to find out online:
- The
setup.cfg
andsetup.py
files are for building distributions. - The
tox.ini
file is for running tests in virtual environments that are created on-the-fly.
In reference to the official AutoKey documentation at https://autokey.github.io/autokey/ Silico_Biomancer (AKA BlueDrink9) said: Iirc on the branch with the docs changes, if you run something like tox -e docs
it should re-generate the files. Should be documented, but probably only on that branch's readme or CONTRIBUTORS.rst
atm
tox -e py
The documentation is in several places, none of which are identical, and some of which aren't served.
- AutoKey 0.94.1 and earlier:
- π Use pre-legacy documentation.
- π Served by: No longer served.
- π Can use some legacy documentation, but some naming conventions changed.
- AutoKey 0.95.0 through AutoKey 0.95.10:
- Use legacy documentation: https://autokey.github.io/autokey/index.html
One of the popular virtual-machine programs is VirtualBox. Below are basic instructions for installing it and using it.
- Go to the VirtualBox LinuxDownloads page.
- Click your GNU/Linux distribution's name in the list to download a .deb file.
- Click the SHA256 checksums link to download a list of SHA checksums.
- Click the MD5 checksums link to download a list of MD5 checksums.
- Open a terminal window in the download folder on your computer.