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

Move security policy to own file #4

Merged
merged 1 commit into from
Oct 17, 2023

Conversation

pnacht
Copy link
Contributor

@pnacht pnacht commented Sep 15, 2023

Fixes #3.

This PR moves Keras' security policy to its own dedicated file for increased visibility.

Signed-off-by: Pedro Kaj Kjellerup Nacht <[email protected]>
@sachinprasadhs sachinprasadhs merged commit d31ff61 into keras-team:master Oct 17, 2023
2 checks passed
@pnacht
Copy link
Contributor Author

pnacht commented Nov 10, 2023

@fchollet @sachinprasadhs I just noticed the security policy was moved back to the CONTRIBUTING.md. It happened in 6d9cd30.

Given the other changes in the commit and the lack of relevant comments in the commit, I suspect this may have been accidental. Am I correct? Shall I resubmit this PR?

@sachinprasadhs
Copy link
Collaborator

@pnacht , It might be because of the source of truth is in g3doc, you can submit the PR again and we can import it internally using copybara.

@pnacht
Copy link
Contributor Author

pnacht commented Nov 13, 2023

Done. #683

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a dedicated file for Keras' security policy
3 participants