d093ce3d84
* fix path to task executable in pyton tests The current approach would copy the current files into the `build/test` directory. Updating the paths according to the custom user setup. By the copy I appended `.py` to have a clear visible distingtion which ones are the python tests. As soon as a source file in the normal directory is changed, it is copied over and the corresponding file is updated. From now on the python tests would need to get run in the according build directory. * reflect the current build instruction in PR template * update paths and globing in run_all * add line break for every cpp test * remove .gitignore in test folder As now all the auxillary files such as `all.log` as well as the executables are present in the `build` directory there is no longer a need to ignore them. * update paths in python test scripts and enable deactivated * remove .py extension when copy to build Further remove glob pattern for `*.t.py` tests. * remove accidentally added template.t from test files
Taskwarrior
Taskwarrior is a command line task list management utility with a multitude of features, developed as a portable open source project with an active and quite vast ecosystem of tools, hooks and extensions.
Install
Taskwarrior is packaged on a wide range of Linux/Unix systems, Mac OS and Windows. Check out the latest available packages in repositories of your OS distribution of choice on Repology.
Alternatively, you can build Taskwarrior from source.
Documentation
The online documentation, downloads, news and more are available on our website, taskwarrior.org.
Community
Taskwarrior has a lively community on many places on the internet.
Best place to ask questions is our discussions forum on Github. For other support options, take a look at taskwarrior.org/support
For code contributions, please use pull requests. See Contributing to Taskwarrior for more details.
Contributing
Your contributions are especially welcome.
Whether it comes in the form of code patches, ideas, discussion, bug reports, encouragement or criticism, your input is needed.
See further development documentation in doc/devel.
Sponsoring
Taskwarrior is a result of work of mostly small group of volunteers, and has been in development since 2006.
If you are a happy Taskwarrior user, please consider sponsoring us through Github Sponsors.
Every sponsorship matters, as it directly increases the number of hours core developers can contribute to the project and makes the project more sustainable.
License
Taskwarrior is released under the MIT license. For details check the LICENSE file.