Taskwarrior

The vit 2.2.0 beta1 pre-release is now available for testing! This important release brings support for TW 2.6 and several new features. If you're a vit user, please consider testing the release out! Read more: github.com/vit-project/vi…

If you don't like bleeding edge, we got your back. Today marks the release of Taskwarrior 2.6.1, the bugfix-only release which improves the upgrade path from 2.5.x series and resolves couple of small bugs that sneaked in 2.6. Thanks to all who contributed! github.com/GothenburgBitF…

@joshmock And we'd be happy to have you! You can also sponsor our work to help us dedicate more time to the project: github.com/sponsors/Gothe…

@joshmock we love you back <3 the bugwarrior problem you have already has a pending fix, we dispatched our first responders directly into the issue

Taskwarrior 2.6.0 is released! This release brings a lot of stability improvements, bug fixes, and several big features - including improvements to contexts, support for XDG spec and environment variables in taskrc. Read more at: github.com/GothenburgBitF…

It's getting hot in the oven! We are down to 4 open issues in our 2.6.0 release milestone. Expect a new release soon 🙂

As Taskwarrior is firmly entering it's teenage years, it's more important than ever that it takes care of its looks. That's why our README recently got a facelift:

Ensuring high performance is on the top of our minds. Recently we fixed important performance bottlenecks, resulting in several-fold increase in execution speed. Despite new features, our 3.0 (June 2021) release is shaping up to be the fastest TW release ever.

This is made possible by having two separate config variables for the context, the "context.<name>.read" and "context.<name>.write". The legacy option of "context.<name>=<filter>" is still supported, but it cannot distinguish between read and write operations.

The task ID 4 gets "project:Work" (the definition of the "work" context applied automatically. For contexts with more complex filters (i.e. with boolean expressions), you can define "read" and "write" subtypes separately (note the "urgent" context below):

Writeable contexts just landed on the development branch of Taskwarrior (2.6.0) today. The context now gets applied as default modifications when creating new tasks, see below:

Check out our new tools page to see what the community provides to enhance Timewarrior: timewarrior.net/tools/ 🛠️ Thanks to all tool/extension authors out there! ♥️

@bano_notit We are working on restoring access. The entire content of the guide is available here: github.com/GothenburgBitF…

@taskwarrior you know that TaskServer setup guide is not available? Are there any other sources of the Guide?

@influxxx Thanks for bringing this up! We're aware of the issue. The documentation is already backed up and will be re-hosted before March 1st.

@taskwarrior a couple of your taskserver links in doco page link to gitpitch. just an fyi :) thanks

@bff81636653 First-class mobile app support is something that is on our radar. Stay tuned for the release of our long-term roadmap!

@taskwarrior Wud be great if there’s an app on iOS

In the past month, we released 2.5.2 ("The best Taskwarrior release in years") and its bugfix successor 2.5.3 ("A small change in codebase, a big step for users"). Read more / download: github.com/GothenburgBitF…

Reasons to upgrade:

@johanbove Lack of volunteers providing data and helping out.

task rc.detection:off rc._forcecolor:on ... | $something_else

@jonwarreninfo You know, the website is open source too...