Issue tracker migration notice #667
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: toolshed/organising#667
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Based on feedback from project participants, we're migrating away from using a single repo for project self-management. The goal is to reduce indirection and open tickets closer "to the source".
This means you can open a ticket on the specific repo where you're facing a problem. For example, the usual suspects:
abra: open an issuedocs.coopcloud.tech: open an issuecoopcloud.tech: open an issuerecipes.coopcloud.tech: open an issueDon't forget to hit "Watch" on the top-right of the repository settings, so you'll get notifications from each repository that you're interested in.
Here's all the recipe repositories. We keep an overview with organisation level projects. If you are not sure or it's a more general issue which affects multiple moving parts, please go ahead and open a ticket in this issue tracker.