Fix DVC merge mistake #221
Conversation
I made a mistake while merging where I overwrote some previous DVC changes. Issue #122
ebrahimebrahim
force-pushed
the
179-add-virtual-fit-transform-to-session-definition
branch
from
0c53b17 to
ecde385
Compare
|
Hey Andrew, sorry about the confusing PR here... What happened is I merged #212 without carefully checking how the DVC data was going to get git-rebased. It ended up wiping out some changes that were already in main 😬 |
|
Sounds good -- I don't know how to review hashes so I'll just make sure the passwords work when pulling the db version in this commit? |
|
That works. You can verify that the password hash changes and new readme that you added are there, while also the virtual fits are updated to the new structuring |
arhowe00
left a comment
arhowe00
left a comment
There was a problem hiding this comment.
Confirmed the presence of User hashes, readme, and virtual fitting results being saved in sessions.
I made a mistake while merging where I overwrote some previous DVC changes in PR #212
This corrects that error, so it brings the DVC database to a manual merge of the state it was in before #212 was merged, and the state it was supposed to be in on my topic branch before the flawed rebase of #212.