Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bundle: commit is commiting the value of a field from the working copy instead of value at stage time #231

Open
erichanson opened this issue Jan 1, 2021 · 0 comments

Comments

@erichanson
Copy link
Member

When bundle.commt() executes, it is not committing the value of a field at the time it was staged, rather it is using the working copy. I sure thought it was architected to copy the value from the working copy to the stage when the staging happened, but it is not doing that, it just uses the current working copy value.

In git terms, this is the scenario where you stage a file and then make more modifications to it. When you commit, it doesn't include modifications made after it was staged unless you stage the changes again.

Investigate and fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant