Things we probably need to do:
- When checking out, track the version we forked from: we can work out local version history from there
- this local version needs to be saved to openfn.yaml probably
- If you make a change and then check out another branch - those changes and history will be lost. We can warn, but there's not a lot else we can do. This is when
project export comes in handy, as I can dump my changes when checking out. We do not automatically "write" local changes back to project.yaml because that's just a view of the app.
- Does the app need to track
forked-from too? No, because the first history item IS the version it was forked from
Versions are compatible if the remote project has no versions since the forked-from version.
After deploying, presumably we need to update forked from. The local project doesn't get removed or anything, so we need to keep maintaining the state
Things we probably need to do:
project exportcomes in handy, as I can dump my changes when checking out. We do not automatically "write" local changes back to project.yaml because that's just a view of the app.forked-fromtoo? No, because the first history item IS the version it was forked fromVersions are compatible if the remote project has no versions since the forked-from version.
After deploying, presumably we need to update forked from. The local project doesn't get removed or anything, so we need to keep maintaining the state