abra app deploy <foobar> doesn't work until a repo is created on gitea #247
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#247
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?
Steps to reproduce
Describe the expected behavior
Deploys a new instance
foobar
using the local recipe.Describe the current behavior
FATA[0004] repository does not exist
Any idea how this might be fixed?
Skipping the check for a remote repo if a local folder already exists. Optionally putting this behaviour behind the exquisite
--chaos
flag.Additional information
abra version 0.3.0-alpha-de7054f
(really
85ff042
, my local-rebase-to-fix-go.sum
is confusing things)abra app new <foobar> doesn't work until a git repo is created on giteato abra app deploy <foobar> doesn't work until a git repo is created on giteaabra app deploy <foobar> doesn't work until a git repo is created on giteato abra app deploy <foobar> doesn't work until a repo is created on giteaHmmm, I think
486a1717e7
might solve that by simply just checking if the local repo is already there? Didn't test it 🙈Still happening but not sure why.
Wondering if it's that deploy calls
EnsureLatest
instead ofEnsureExists
, which then tries to do agit checkout
.Pushed
4a245c3e02
and1f6e4fa4a3
as part of smoking out issues here. Might be fixed then!Lemme know if this is still happening, closing for now 🌇