-
Notifications
You must be signed in to change notification settings - Fork 382
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
gitignore incompatibility with *~ #5059
Comments
I think there's a feature request about newly-tracked ignored files, something like making |
so if I understand correctly, any jj command takes a snapshot, making a that matches what I see,
the behavior is logical in retrospect, but maybe could be mentioned more explicitly in the docs. |
Correct. A working-copy change is a commit in jj.
Do you have any suggestion? It's documented in tutorial, but the Git comparison table might be a better place. https://martinvonz.github.io/jj/latest/tutorial/#creating-our-first-change |
"jj gitignore" on google doesn't bring up the tutorial in the first 10 results. instead, the first page is https://martinvonz.github.io/jj/latest/git-compatibility/, which just says " Ignores in .gitignore files are supported. So are ignores in .git/info/exclude or configured via Git's core.excludesfile config. The .gitignore support uses a native implementation, so please report a bug if you notice any difference compared to git." maybe something like "Patterns for untracked files in .gitignore files are supported. So are ignores in .git/info/exclude or configured via Git's core.excludesfile config. For tracked files, see 'jj untrack'. The .gitignore support uses a native implementation, ... " |
It could also mention that if you know you need a pattern ignored, make the ignore file before the |
thanks, Yuya! |
Description
I have trouble convincing jj to leave emacs backup files alone in new repos.
I am a bit stumped, because I have another repo on another machine where I got this to work, but I can't recall what I tweaked there.
Specifications
The text was updated successfully, but these errors were encountered: