Repositories docs reference (#11840)
* doc: Adds docs for reference field on package repo * fixes double space * minor grammar fixpull/11844/head
parent
690fe716c5
commit
9acf6bc0a1
|
@ -548,6 +548,14 @@ Here is an example for the smarty template engine:
|
||||||
|
|
||||||
Typically, you would leave the source part off, as you don't really need it.
|
Typically, you would leave the source part off, as you don't really need it.
|
||||||
|
|
||||||
|
If a source key is included, the reference field should be a reference to the version that will be installed.
|
||||||
|
Where the type field is `git`, this will the be the commit id, branch or tag name.
|
||||||
|
|
||||||
|
**Note**: It is not recommended to use a git branch name for the reference field. While this is valid since it is supported by `git checkout`,
|
||||||
|
branch names are mutable so cannot be locked.
|
||||||
|
|
||||||
|
Where the type field is `svn`, the reference field should contain the reference that gets appended to the URL when running `svn co`.
|
||||||
|
|
||||||
> **Note**: This repository type has a few limitations and should be avoided
|
> **Note**: This repository type has a few limitations and should be avoided
|
||||||
> whenever possible:
|
> whenever possible:
|
||||||
>
|
>
|
||||||
|
|
Loading…
Reference in New Issue