jj/cli
David Crespo bf24be20ef new: swap order of @ and main in doc comment
I followed the recommendation in the `jj new` doc to use `jj new main @`
to make a merge commit and ended up with a merge commit that GitHub did
not like. The PR diff included both the relevant changes from that
branch plus everything I merged in. @papertigers pointed out that
swapping the two args produces a merge commit GitHub understands better.
Happy to add a line explaining that the order matters, but it might be
too much detail for this spot. The linked doc
https://martinvonz.github.io/jj/latest/working-copy/ also does not
explain this.
2024-12-14 00:47:30 +01:00
..
examples working_copy: plumbing to propagate untracked paths to caller 2024-12-11 20:19:51 +09:00
src new: swap order of @ and main in doc comment 2024-12-14 00:47:30 +01:00
testing style: inline variables into format strings 2024-10-04 22:29:13 +02:00
tests new: swap order of @ and main in doc comment 2024-12-14 00:47:30 +01:00
build.rs build: fix cargo publish by symlinking cli/docs->docs 2024-11-05 17:37:14 -08:00
Cargo.toml cargo: drop dependency on config crate 2024-12-10 16:08:50 +09:00
docs build: fix cargo publish by symlinking cli/docs->docs 2024-11-05 17:37:14 -08:00
LICENSE cargo: add LICENSE file to each crate we publish 2023-09-22 21:48:28 -07:00