Naming scheme for Drone orgsecrets #118
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#118
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?
Currently, we have a mixture of formats:
I think having some kind of standard might help:
(And easier if we end up migrating Gitea again 😛)
What about (although no strong preferences, just a suggestion):
<service>[_<host>]_<username>_<type>
Which might make
matrix_chat.autonomic.zone_autono-bot_password
dockerhub_thecoopcloud_password
(no<host>
, implied by<service>
)drone_build.coopcloud.tech_coop-cloud_token
While we're at it, maybe we can standardise on either
passwd
orpassword
for<type>
? Prefer "password", but think either would be better than both 🧘