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

New Issue

2022-05-16T14:24:41Z

decentral1se commented

2022-05-16 14:24:41 +00:00

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 referenced this issue

2023-02-18 22:55:06 +00:00

Support multiple app catalogues #139

decentral1se added this to the (deleted) project 2023-06-08 09:19:51 +00:00

decentral1se commented

2023-07-25 13:18:27 +00:00

I think this could be the cause of several issues tbh.

coop-cloud/organising#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

decentral1se referenced this issue from a commit

2023-07-26 06:18:05 +00:00

fix: only use git to update local catalogue

decentral1se commented

2023-07-26 06:19:33 +00:00