fluxcd
/
source-controller
mirror of https://github.com/fluxcd/source-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

gitrepo: document limitation of `spec.ref.name` with Azure Devops 

Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
This commit is contained in:
Sanskar Jaiswal 2023-07-24 13:26:39 +05:30
parent 7f40be76e9
commit 8d16f187e6
No known key found for this signature in database
GPG Key ID: 5982D0279C227FFD
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/spec/v1/gitrepositories.md
View File

@ -319,6 +319,12 @@ Valid examples are: `refs/heads/main`, `refs/tags/v0.1.0`, `refs/pull/420/head`,
This field takes precedence over [`.branch`](#branch-example), This field takes precedence over [`.branch`](#branch-example),
[`.tag`](#tag-example), and [`.semver`](#semver-example). [`.tag`](#tag-example), and [`.semver`](#semver-example).
**Note:** Azure DevOps and AWS CodeCommit do not support fetching the HEAD of
a pull request. While Azure DevOps allows you to fetch the merge commit that
will be created after merging a PR (using `refs/pull/<id>/merge`), this field
can only be used to fetch references that exist in the current state of the Git
repository and not references that will be created in the future.
#### Commit example #### Commit example
To Git checkout a specified commit, use `.spec.ref.commit`: To Git checkout a specified commit, use `.spec.ref.commit`: