Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/xavdid/linear-task-tree
Create trees of dependent Linear tasks from the CLI
https://github.com/xavdid/linear-task-tree
bun cli dependent-tasks linear productivity
Last synced: about 1 month ago
JSON representation
Create trees of dependent Linear tasks from the CLI
- Host: GitHub
- URL: https://github.com/xavdid/linear-task-tree
- Owner: xavdid
- Created: 2023-09-19T06:46:53.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-09-18T07:37:20.000Z (4 months ago)
- Last Synced: 2024-12-08T16:45:29.997Z (about 1 month ago)
- Topics: bun, cli, dependent-tasks, linear, productivity
- Language: TypeScript
- Homepage:
- Size: 196 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
Awesome Lists containing this project
README
# linear-task-tree
A script to create a parent task and many subtasks in [Linear](https://linear.app/).
> note: this is mostly for personal use so you won't be able to run it directly. Might be useful for learning though!
## Structure
Running this script gives you a single parent task and 1+ subtasks. Each subtask can declare blockers on other tasks. They'll all share a status and label.
## Motivation
Setting up my preferred dependent task setup took too many clicks in the UI, so I condensed it into a more refined script. I described that setup briefly to Linear support as follows:
---
My big needs for a project / epic are to:
1. be able to mark an issue as part of a larger initiative
2. See progress on the initiative (preferably as a `done/total` or a visual indicator)
3. Apply a component label to the project and everything under it, so I can tie work back to a specific codebaseI don't care about:
- which teams(s) are assigned (I use this as a solo dev)
- who the lead is (it's always me!)
- start/end dates (would love "hide until" dates for individual tasks, but don't need it for project-level things)My main view is "Active issues", which shows tasks in todo / in progress / blocked. When I use parent issues, I can see more of the title on the sub issues and there's more relevant data on the task:
![](https://cdn.zappy.app/e056a4a78556ecaf0f4fdfc2f3534ebe.png)
Also, I can make a view for my parent issues and see them all (and their progress / status) in a single place:
![](https://cdn.zappy.app/ecfaf2c6e4e61afc588e9548ed263d12.png)
the projects view is much less useful:
![](https://cdn.zappy.app/604c7da488b4338bd92b5fd418d7ff99.png)
So I get nearly everything I need from parent issues, except for having to check their status and manually start/close them when their children are done.
### Advent of Code
This also includes a script to create a bunch of tasks for [Advent of Code](https://adventofcode.com/) following the above structure.
## Development:
Development tasks are run using [just](https://github.com/casey/just).
To install dependencies:
```bash
just install
```To compile the code for use during development:
```bash
just dev
```To run:
```bash
just run
```To run the Advent of Code script:
```bash
just aoc
```