Abra doesn't use git to update the local catalogue copy #321

Closed
opened 2022-05-16 14:24:41 +00:00 by decentral1se · 2 comments
Owner

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.

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.
decentral1se added the
bug
abra
labels 2022-05-16 14:24:41 +00:00
decentral1se added this to the Beta release (software) project 2022-05-16 14:24:43 +00:00
decentral1se modified the project from Beta release (software) to (deleted) 2022-08-05 11:48:30 +00:00
decentral1se added this to the Critical fixes project 2023-06-08 09:19:51 +00:00
Author
Owner

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.

I think this could be the cause of several issues tbh. https://git.coopcloud.tech/coop-cloud/organising/issues/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.
decentral1se self-assigned this 2023-07-25 20:06:01 +00:00
Author
Owner
https://git.coopcloud.tech/coop-cloud/abra/commit/ab64eb2e8dbac8f337ffa6bfbf687a6e63d7c910
decentral1se started working 2023-07-26 06:21:25 +00:00
decentral1se added spent time 2023-07-26 06:21:35 +00:00
20 minutes
decentral1se canceled time tracking 2023-07-26 06:21:43 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Total Time Spent: 20 minutes
decentral1se
20 minutes
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#321
No description provided.