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
It seems that change to an existing file in the repo can be git bigstore push correctly, but if I git add/stage a NEW file and add that file to .gitattributes, the git bigstore push won't directly work. I think the reason is that in the pathnames() function, it uses ls_tree to list all the files, but a new file won't be listed here since it hasn't been added to the tree?
I guess one way to solve that is to use ls_files with the stage option instead to list all the files. But I am not sure whether I missed something or I misunderstood the intentional workflow.
If this is actually a problem, I am happy to submit a patch.
The text was updated successfully, but these errors were encountered:
Hmm, interesting. This might be a bug; do you have a good reproducible test case we can test against? I think the intended behavior should be what you're describing though, a patch would be great!
It seems that change to an existing file in the repo can be
git bigstore push
correctly, but if I git add/stage a NEW file and add that file to .gitattributes, thegit bigstore push
won't directly work. I think the reason is that in thepathnames()
function, it usesls_tree
to list all the files, but a new file won't be listed here since it hasn't been added to the tree?I guess one way to solve that is to use
ls_files
with the stage option instead to list all the files. But I am not sure whether I missed something or I misunderstood the intentional workflow.If this is actually a problem, I am happy to submit a patch.
The text was updated successfully, but these errors were encountered: