Abra doesn't use git to update the local catalogue copy #321
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
Total Time Spent: 20 minutes
Due Date
decentral1se
20 minutes
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#321
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?
We're still using the original implementation of polling the meta of the catalogue and then pulling down a new copy of it. Instead, we should be git pulling the latest copy since we're using a git repository now, not a single JSON file.
I think this could be the cause of several issues tbh.
#462 is pretty illustrative of this. The internal logic just pulls down latest changes into the repository because they're just published. However, then the local catalogue repository is dirty and stops stuff happening.
We should just automatically
git pull
the latest before doing generate work and git commit / push the generated changes we make.ab64eb2e8d