The case for making --status/-S the default on abra app ls #189
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#189
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the problem to be solved
The default of
abra app ls
doesn't give you the full story now.We did that for performance issues but now Go is making things go faster.
It even runs relatively OK on my shitty connection, how is it for other folks?
This is the
--status/-S
output now (see attachments).Describe the solution you would like
abra app ls
is giving us the max info possible while staying snappy and responsive is the ideal situation. So remove--status/-S
and making it the default or adding a--no-status/-ns
to turn it off when you don't want it?Leaving aside for now.