Scaling Mise to large organizations with too many tasks #3436
stevelandeyasana
started this conversation in
Ideas
Replies: 2 comments 3 replies
-
Beta Was this translation helpful? Give feedback.
3 replies
-
Here's what I came up with to serve my needs: [tasks.search]
run = """
#!/usr/bin/env zsh
set -e
TASK=$(exec mise tasks ls --json | jq '.[] | .name + " - " + .description' --raw-output | fzf --preview='mise task info {+1}' | cut -d' ' -f1 | tr -d '[:space:]')
if [[ $TASK ]]; then
echo "mise run $TASK"
exec mise run $TASK
else
echo "Aborted"
fi
""" Improvements over @syhol's solution:
I wish the description printed on the line could be in a dimmer color, which is where Mise itself could have a better implementation. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I work at an organization with its own custom task runner that is the canonical entry point to all our internal tools. Mise can do most things our custom task runner can do, but there are UX problems that would prevent it from scaling.
Today,
mise task ls
gives you a nice 3-column table with Name, Description, and Source. For example...Now suppose there are 500 tasks, with some nested 3 groups deep, and you joined the company last week so you don't know exactly what something is called.
One way of addressing this would be to add a new command such as
mise task search
which would let you interactively fuzzy-find a task. Does that seem like a reasonable addition to this project, or is Mise not a good fit for this use case?I'd also love for some way to type a prefix and have Mise show me all the tasks with that prefix. Maybe it can already do this and I missed it.
Beta Was this translation helpful? Give feedback.
All reactions