abra app deploy <foobar> doesn't work until a repo is created on gitea #247
Closed
opened 2021-11-14 19:00:24 +00:00 by 3wordchant
·
4 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#247
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Steps to reproduce
Describe the expected behavior
Deploys a new instance
foobarusing the local recipe.Describe the current behavior
FATA[0004] repository does not existAny 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
--chaosflag.Additional information
abra version 0.3.0-alpha-de7054f(really
85ff042, my local-rebase-to-fix-go.sumis 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
486a1717e7might 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
EnsureLatestinstead ofEnsureExists, which then tries to do agit checkout.Pushed
4a245c3e02and1f6e4fa4a3as part of smoking out issues here. Might be fixed then!Lemme know if this is still happening, closing for now 🌇