Consider Gitea new features: Go package repositories, Actions CI #473
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#473
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?
With https://docs.gitea.com/next/usage/actions/overview we could avoid using the
$current_CI
solution which has licensing issues in general and there has also been a fork in the community. Unsure how much of an issue this is but consolidating on Gitea would be cool? Also$current_CI
has various security considerations for running, maybe Gitea has less issues in this regard? They're using https://gitea.com/gitea/act_runner which I haven't looked into deeply....https://docs.gitea.com/next/usage/packages/go could also help us with Go code hosting & publishing which is not a major issue now. However, we could consider removing the hack from the website to provide the vanity URLs for downloading our code? Would be again a step towards consolidation.
Unsure how feasible this all is given the Gitea / Forgejo issue also... where to commit ourselves to?
Related:
Will pop up again if the need arises.