mirror of
https://github.com/martinvonz/jj.git
synced 2024-11-28 09:14:04 +00:00
trunk() docs fix: commits aren't tried in order; newest commit wins
That's my understanding of how `latest()` revset works.
This commit is contained in:
parent
f39b0d24c8
commit
0c31e0ba61
1 changed files with 3 additions and 2 deletions
|
@ -167,8 +167,9 @@ See [revsets.toml](https://github.com/martinvonz/jj/blob/main/cli/src/config/rev
|
|||
for a comprehensive list.
|
||||
|
||||
* `trunk()`: Resolves to the head commit for the trunk branch of the `origin`
|
||||
remote. The branches `main`, `master`, and `trunk` are tried in order.
|
||||
If none of the branches exist, it evaluates to `root()`.
|
||||
remote. The branches `main`, `master`, and `trunk` are tried. If more than one
|
||||
potential trunk commit exists, the newest one is chosen. If none of the
|
||||
branches exist, the revset evaluates to `root()`.
|
||||
|
||||
You can [override](./config.md) this as appropriate. If you do, make sure it
|
||||
always resolves to exactly one commit. For example:
|
||||
|
|
Loading…
Reference in a new issue