diff --git a/main/FAQ.html b/main/FAQ.html new file mode 100644 index 000000000..5d3fe7ddf --- /dev/null +++ b/main/FAQ.html @@ -0,0 +1,16 @@ + + +
jj log
Is your commit visible with jj log -r 'all()'?
jj log -r 'all()'
If yes, you should be aware that jj log only shows the revisions matching -revsets.log by default. You can change it as described in config to show +revsets.log by default. You can change it as described in config to show more revisions.
revsets.log
If not, the revision may have been abandoned (e.g. because you used jj abandon, or because it's an obsolete version that's been rewritten with jj rebase, jj describe, etc). In that case, jj log -r commit_id should show the revision as "hidden". jj new commit_id should make the revision visible again.
jj abandon
jj rebase
jj describe
jj log -r commit_id
jj new commit_id
See revsets and templates for further guidance.
Jujutsu automatically records new files in the current working-copy commit and doesn't provide a way to prevent that.