Skip to content

Commit bdafb2f

Browse files
committed
adding info item on api key warning from github
1 parent a026751 commit bdafb2f

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

docs/getting-started/installation.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ This template is a minimal setup intended for creating your own study project qu
1818

1919
This is the preferred approach when you do not need cutting-edge changes (for example, from `dev`) and want a more stable baseline to build from. Unlike a fork, the new repository is not linked to the upstream repository's fork network, which helps keep your project lightweight and focused on your own study. You can also create as many repositories as you want from the template, which is not possible with forking.
2020

21+
:::info
22+
Most likely, you will **receive a warning from GitHub about a potential security issue** as an API key is being shared, with a subject like “Possible valid secrets detected“.
23+
You can safely ignore this warning. The reason for this is that the Firebase API key is not a secret key, and it is intended to be shared publicly in client-side code. For more information, see the [Firebase documentation on API keys](https://firebase.google.com/docs/projects/api-keys#api_key_security_recommendations).
24+
:::
2125

2226
## Forking Repository (Advanced Alternative to Template Repository)
2327

0 commit comments

Comments
 (0)