Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port API Key security suggestions to the README #119

Open
logankilpatrick opened this issue Apr 16, 2024 · 1 comment
Open

Port API Key security suggestions to the README #119

logankilpatrick opened this issue Apr 16, 2024 · 1 comment
Assignees
Labels
component:documentation Improvements or additions to documentation status:awaiting user response Awaiting a response from the author status:triaged Issue/PR triaged to the corresponding sub-team type:feature request New feature request or enhancement

Comments

@logankilpatrick
Copy link
Member

Right now, in the README, we suggest people not check their API key into the repo, we should do the same in this README like we do in the docs: https://ai.google.dev/tutorials/quickstart#android

@singhniraj08 singhniraj08 added type:bug Something isn't working component:documentation Improvements or additions to documentation type:feature request New feature request or enhancement status:triaged Issue/PR triaged to the corresponding sub-team and removed type:bug Something isn't working labels Apr 18, 2024
@rlazo
Copy link
Collaborator

rlazo commented Apr 18, 2024

Hi @logankilpatrick could you elaborate? The installation and usage section of the repo's README point to the quickstart you linked.

Is your suggestion that we include API Key security recommendations within the readme itself instead that in the pointed doc?

@rlazo rlazo added the status:awaiting user response Awaiting a response from the author label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:documentation Improvements or additions to documentation status:awaiting user response Awaiting a response from the author status:triaged Issue/PR triaged to the corresponding sub-team type:feature request New feature request or enhancement
Projects
None yet
Development

No branches or pull requests

3 participants