Record results from testing

Update specifying-dependencies.md to show not specifying the branch for git doesn't always use the main branch.
This commit is contained in:
c-git 2023-06-10 10:26:06 -04:00 committed by GitHub
parent 928b9561c1
commit 8a1d6fd2db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -140,7 +140,8 @@ Cargo will fetch the `git` repository at this location then look for a
of a workspace and setting `git` to the repository containing the workspace).
Since we havent specified any other information, Cargo assumes that
we intend to use the latest commit on the main branch to build our package.
we intend to use the latest commit on the Default ("base") branch branch
to build our package, which may not necessarily be the main branch.
You can combine the `git` key with the `rev`, `tag`, or `branch` keys to
specify something else. Here's an example of specifying that you want to use
the latest commit on a branch named `next`: