Retiring recipes #603
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#603
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?
I guess currently removing the "recipe" topic, manually removing it from https://git.coopcloud.tech/coop-cloud/recipes-catalogue-json, and archiving the repo would fix it.
But wouldn't it be nice if archiving the repo automatically skipped it from catalogue generation? And maybe even caused
abra catalogue generate
to remove it?An enby can dream...
I think this is in connection with #569 and possibly related to #604 which, I just opened but I think compliments this
Archive -> Ignore
idea well.