The sound distributed version control system

#645 I can't do `pijul add Cargo.lock`

Opened by jvff on February 2, 2022
jvff on February 2, 2022

I’ve tried updating the .ignore file, and its contents are:

.git
target

But I still can’t get pijul add Cargo.lock to make Cargo.lock appear in pijul ls.

I’m not sure what I’m doing wrong :(

pmeunier on February 3, 2022

Hi! And thanks for the report. Unfortunately, I can’t reproduce (as you can see that this repository has a Cargo.lock). If you want, you can send a tarball of the repository (including the .pijul subdirectory) to pe@pijul.org

jvff on February 7, 2022

Hi! Thanks for the quick reply. I’m sorry it took a while for me to reply, I was trying to reproduce the issue in a clean repository and I couldn’t. However, after a while I did find the cause. The directory I was using for the repository had a .gitignore file that did have Cargo.lock inside it. So the issue was that I missed that .gitignore also affected the files Pijul would ignore.

I’m not sure if there’s any other action that needs to be taken, like documenting this somewhere if it’s not already documented. Otherwise, I think this issue can be closed.

Thanks!

coconut on February 28, 2022

I would have never guessed that pijul would ignore files residing in file .gitignore besides .ignore. This should be documented for sure if this is the case, but I think it should not care about .gitignore at all. If one is using git, use .gitignore, if you are using pijul, use .ignore! I do not think that it is pijul’s job to mix it up in this way. If one wants, they could just rename .gitignore to .ignore. I remember seeing a way to convert a git repository to pijul. If this is really true that such a thing exists, then that should involve this rename.