summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIoannis Papapanagiotou <[email protected]>2025-07-11 16:29:05 +0300
committerGitHub <[email protected]>2025-07-11 13:29:05 +0000
commit62ebd51e111c2e1623e1417455307d1d0151826c (patch)
tree10f7e271a43577031e49537edf024e011c55f119
parente8fd2d6147a6527d852d85842bf250400ec93b49 (diff)
docs: correct typo in CONTRIBUTING.md (#3852)
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c8d866e9..5d865959 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -76,7 +76,7 @@ In the PR description, explain the "why" behind your changes and link to the rel
## Forking
-If you are forking the repository you will be able to run the Built, Test and Integration test workflows. However in order to make the integration tests run you'll need to add a [GitHub Repository Secret](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository) with a value of `GEMINI_API_KEY` and set that to a valid API key that you have available. Your key and secret are private to your repo; no one without access can see your key and you cannot see any secrets related to this repo.
+If you are forking the repository you will be able to run the Build, Test and Integration test workflows. However in order to make the integration tests run you'll need to add a [GitHub Repository Secret](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository) with a value of `GEMINI_API_KEY` and set that to a valid API key that you have available. Your key and secret are private to your repo; no one without access can see your key and you cannot see any secrets related to this repo.
Additionally you will need to click on the `Actions` tab and enable workflows for your repository, you'll find it's the large blue button in the center of the screen.