about summary refs log tree commit diff
path: root/src/test/rustdoc-ui/coverage/enum-tuple.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-01-06 21:51:44 +0000
committerbors <bors@rust-lang.org>2023-01-06 21:51:44 +0000
commit7ac9572c48435b5342ad3550d6036bde835d37dc (patch)
tree5d084e243ed2d75bfb1249f60a339ac2597c8c0e /src/test/rustdoc-ui/coverage/enum-tuple.rs
parent0fb8b72ce49997d60a631e921d2cf5be9ca229e6 (diff)
parentd5e5762211a6c8ee22b789c15596d2b49a45ed3f (diff)
downloadrust-7ac9572c48435b5342ad3550d6036bde835d37dc.tar.gz
rust-7ac9572c48435b5342ad3550d6036bde835d37dc.zip
Auto merge of #106415 - Nilstrieb:where-is-my-master-branch, r=jyn514
Handle non-existent upstream master branches in `x fmt`

People who do have a remote for `rust-lang/rust` but don't have the master branch checked out there used to get this error when running `x fmt`:
> fatal: ambiguous argument 'rust/master': unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git <command> [<revision>...] -- [<file>...]'
> rust/master

Which is not exactly helpful.

Now, we fall back to `origin/master` (hoping that at least that remote exists) for that case. If there is still some error, we just fall back to `x fmt .` and print a warning.

r? `@jyn514`
Diffstat (limited to 'src/test/rustdoc-ui/coverage/enum-tuple.rs')
0 files changed, 0 insertions, 0 deletions