You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We pull from the source repository.
Within the target repository we can loose the information about the last pulled git hash.
E.g. because of squashed commits. Github will keep those dangling commits some time but will most likely be garbage collected.
To keep the hash within the target repository the commit should be tagged with a version.
Current idea is to use something like the branch name <templatesync_hash>.
It needs to be possible to get an order of those tags to be able to find the last one.
Use Case
The current deletion of files feature is buggy and not working.
To be able to find all deleted remote files the last merge hash must be known.
Proposed Solution
Add the hash and push it together with the branch.
Acknowledgements
I may be able to implement this feature request
The text was updated successfully, but these errors were encountered:
Describe the feature
We pull from the source repository.
Within the target repository we can loose the information about the last pulled git hash.
E.g. because of squashed commits. Github will keep those dangling commits some time but will most likely be garbage collected.
To keep the hash within the target repository the commit should be tagged with a version.
Current idea is to use something like the branch name <templatesync_hash>.
It needs to be possible to get an order of those tags to be able to find the last one.
Use Case
The current deletion of files feature is buggy and not working.
To be able to find all deleted remote files the last merge hash must be known.
Proposed Solution
Add the hash and push it together with the branch.
Acknowledgements
The text was updated successfully, but these errors were encountered: