summaryrefslogtreecommitdiff
path: root/github-management/setting-up-cla-check.md
diff options
context:
space:
mode:
authorChristoph Blecker <admin@toph.ca>2018-06-26 12:52:25 -0700
committerChristoph Blecker <admin@toph.ca>2018-06-26 12:52:25 -0700
commit5d635348ababd1ace7ec1cd4e92ce71b594dd9bd (patch)
treeb663cd9e6adfc41f398758350154f0773a783252 /github-management/setting-up-cla-check.md
parent9ce2bdc3bb1a9e5b0acea5a4a2dbe8870041de28 (diff)
Add README to github-management
Diffstat (limited to 'github-management/setting-up-cla-check.md')
-rw-r--r--github-management/setting-up-cla-check.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/github-management/setting-up-cla-check.md b/github-management/setting-up-cla-check.md
index bb344190..d679b804 100644
--- a/github-management/setting-up-cla-check.md
+++ b/github-management/setting-up-cla-check.md
@@ -13,7 +13,7 @@ the Linux Foundation CNCF CLA check for your repositories, please read on.
- Payload URL: https://identity.linuxfoundation.org/lfcla/github/postreceive?group=284&comment=no&target=https://identity.linuxfoundation.org/projects/cncf
- `group=284` specifies the ID of the CNCF project authorized committers group in our CLA system.
- `comment=no` specifies that our system should not post help comments into the pull request (since the Kubernetes mungebot does this).
- - `target=https://identity.linuxfoundation.org/projects/cncf` specifies what will be used for the "Details" link in Github for this status check.
+ - `target=https://identity.linuxfoundation.org/projects/cncf` specifies what will be used for the "Details" link in GitHub for this status check.
- Content Type: 'application/json'
- Secret: Please contact [@idvoretskyi](mailto:ihor@cncf.io), and [@caniszczyk](mailto:caniszczyk@linuxfoundation.org).
- Events: Let me select individual events
@@ -56,5 +56,5 @@ the same org/repo, to ensure that it can add labels `cncf-cla: yes` and `cncf-cl
on the status published by the Linux Foundation webhook.
The label automation may not be essential for your repository, if you’re not using merge
-automation. For repos with maintainers doing manual merges, github protected branches may
+automation. For repos with maintainers doing manual merges, GitHub protected branches may
suffice.