Inconsistencies in bookmark doc

[nickchomey]

https://github.com/steveklabnik/jujutsu-tutorial/blob/main/src/sharing-code/named-branches.md

The first couple logs show that trunk is on povouosx, but then later it is on ytkvxlpy. Then it switches back to povouosx

The dates show that the example started on 2024-03-01, then 03-17, then back to 03-01

It would be easier to follow if it was all consistent

[drieber]

I am piggybacking on this issue. I am new to jj and I am currently reading https://steveklabnik.github.io/jujutsu-tutorial/sharing-code/remotes.html
Either I did something wrong or there is something wrong with parts of this chapter. There is a sequence that goes like this (some steps omitted):

jj git remote add origin git@github.com:steveklabnik/jj-hello-world.git
...
jj bookmark set trunk --allow-backwards
...
jj git push

That git push fails for me:

$ jj git push
Warning: Refusing to create new remote bookmark trunk@origin
Hint: Use --allow-new to push new bookmark. Use --remote to specify the remote to push to.
Nothing changed.
[hi on] drieber@rieber:~/jj-book/hello-world$ jj git push --allow-new
Changes to push to origin:
  Add bookmark trunk to fcb7a59ca253
Error: invalid or unknown remote ssh hostkey; class=Ssh (23); code=Certificate (-17)
Hint: Jujutsu uses libssh2, which doesn't respect ~/.ssh/config. Does `ssh -F /dev/null` to the host work?

I have to admit I am not a git expert by any means, so maybe that explains my confusion? Am I supposed to first clone https://github.com/steveklabnik/jj-hello-world and work on that?

[drieber]

I could file a separate issue if necessary.

[kastl-ars]

@drieber At least from the brief list of commands I am missing some kind of "jj git fetch". This explains why jj thinks the bookmark is new and it does not move it, but wants to add it to the commit.

The SSH error below means that JJ could not talk to the remote, so I daresay my guess about jj git fetch is correct. You need to put Github ssh host keys into your ~/.ssh/known_hosts.

github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
github.com ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCj7ndNxQowgcQnjshcLrqPEiiphnt+VTTvDP6mHBL9j1aNUkY4Ue1gvwnGLVlOhGeYrnZaMgRK6+PKCUXaDbC7qtbW8gIkhL7aGCsOr/C56SJMy/BCZfxd1nWzAOxSDPgVsmerOBYfNqltV9/hWCqBywINIR+5dIg6JTJ72pcEpEjcYgXkE2YEFXV1JHnsKgbLWNlhScqb2UmyRkQyytRLtL+38TGxkxCflmO+5Z8CSSNY7GidjMIZ7Q4zMjA2n1nGrlTDkzwDCsw+wqFPGQA179cnfGWOWRVruj16z6XyvxvjJwbz0wQZ75XK5tKSb7FNyeIEs4TT4jk+S4dhPeAUC5y+bDYirYgM4GC7uEnztnZyaVWQ7B381AK4Qdrwt51ZqExKbQpTUNn+EjqoTwvqNj4kqx5QUCI0ThS/YkOxJCXmPUWZbhjpCg56i+2aB6CmK2JGhn57K5mj0MNdBXA4/WnwH6XoPWJzK5Nyu2zB3nAZp+S5hpQs+p1vN1/wsjk=

And for the next time filing a separate issue would be better than piggybacking, even if your question is about the same section.

[steveklabnik]

@drieber yeah the behavior of jj git push changed recently that breaks this doc. you need to pass --allow-new

[drieber]

@drieber yeah the behavior of jj git push changed recently that breaks this doc. you need to pass --allow-new

Is that it? Should there be a jj git fetch somewhere? Should readers clone git@github.com:steveklabnik/jj-hello-world.git first?

[steveklabnik]

Maybe, if you don't have github in your known hosts yet?