__git: impossible to update after first-use #47

New issue

Open

opened 2021-11-20 11:25:09 +00:00 by ungleich-gitea · 2 comments

ungleich-gitea commented

2021-11-20 11:25:09 +00:00

Owner

Expectation:
after using something like __git stuff --branch production for the first time, I'd expect subsequent runs of a manifest with that to keep the stuff repository up to date with the remote production branch.

Actual behaviour:
a fetch of the repository never happens if the repository is already cloned.

Proposal:
I can think of two options:

Have a __git/explorer/needs-update explorer that: if the repository is already cloned, does a git fetch and compares the current HEAD with the remote HEAD, then echoes YES if they differ and NO if they are equal. Afterwards in gencode-remote we would git pull if and only if necessary.
Always generate code in gencode-remote that does the fetching and comparing (wouldn't be necessary on first run).

Thoughts?

As with #818, I am currently working with __git so it'd be relatively low effort to fix this.

Expectation: after using something like `__git stuff --branch production` for the first time, I'd expect subsequent runs of a manifest with that to keep the `stuff` repository up to date with the remote `production` branch. Actual behaviour: a fetch of the repository never happens if the repository is already cloned. Proposal: I can think of two options: 1. Have a `__git/explorer/needs-update` explorer that: if the repository is already cloned, does a `git fetch` and compares the current HEAD with the remote HEAD, then echoes `YES` if they differ and `NO` if they are equal. Afterwards in `gencode-remote` we would `git pull` if and only if necessary. 2. Always generate code in `gencode-remote` that does the fetching and comparing (wouldn't be necessary on first run). Thoughts? As with #818, I am currently working with `__git` so it'd be relatively low effort to fix this.