If I'm reading correctly this translates PRs into test tickets? Is that a workflow that a lot of teams use? We usually just flow the feature ticket from grooming to dev, to code review to QA, then release.
This workflow has historically worked for us quite well. We merge in features rapidly so having GitHub be the source of truth for activity that needs to be tested is beneficial for never accidentally missing items.
FYI we used to use Trello (using the same workflow) but switched to Jira and wrote this tool in the process. Jira aggregation in the web app can be quite slow so actually this tool makes tracking a bit nicer as well.
It is awesome to see the increase in popularity of `rich` and `textual` libraries! Check them out if you want to develop a TUI application or just make sure your CLI app looks awesome. @willmcgugan is doing a great job! <3
Love to see the use of `httpx` as well, a great Python HTTP client with support for both sync and async APIs.
10 comments
[ 3.4 ms ] story [ 27.7 ms ] threadFYI we used to use Trello (using the same workflow) but switched to Jira and wrote this tool in the process. Jira aggregation in the web app can be quite slow so actually this tool makes tracking a bit nicer as well.
Love to see the use of `httpx` as well, a great Python HTTP client with support for both sync and async APIs.