summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDerek Mauro <dmauro@google.com>2021-09-16 13:00:21 -0400
committerDerek Mauro <dmauro@google.com>2021-09-16 13:00:21 -0400
commit40dfd4b775a66979ad1bd19321cdfd0feadfea27 (patch)
treecb971e73051aed2e66e7c53b2fb46d477d729ea5
parent6bfab0beccaab26d8d3762912b7ccda66e6281ef (diff)
parent061973710efe0a8e1533fbee13ed7f6dcf13fd02 (diff)
downloadgoogletest-git-40dfd4b775a66979ad1bd19321cdfd0feadfea27.tar.gz
Merge pull request #3519 from AkashKumarSingh11032001:master
PiperOrigin-RevId: 397082478
-rw-r--r--CONTRIBUTING.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index da45e445..5bdead53 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -36,7 +36,8 @@ PR is acceptable as an alternative.
This ensures that work isn't being duplicated and communicating your plan
early also generally leads to better patches.
4. If your proposed change is accepted, and you haven't already done so, sign a
- Contributor License Agreement (see details above).
+ Contributor License Agreement
+ ([see details above](#contributor-license-agreements)).
5. Fork the desired repo, develop and test your code changes.
6. Ensure that your code adheres to the existing style in the sample to which
you are contributing.