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 #18385

Closed
wants to merge 1 commit into from

Conversation

pnacht
Copy link
Contributor

@pnacht pnacht commented Sep 13, 2023

Fixes keras-team/tf-keras#137.

This PR moves the Keras security policy to a dedicated file, increasing its discoverability by adding a new "issue type" and displaying the policy in the project's security dashboard.

I recommend creating this file in the keras-team/.github repository, which would set a default policy visible in all keras-team repositories.

@sachinprasadhs sachinprasadhs added the keras-team-review-pending Pending review by a Keras team member. label Sep 13, 2023
@divyashreepathihalli divyashreepathihalli removed the keras-team-review-pending Pending review by a Keras team member. label Sep 14, 2023
@google-ml-butler google-ml-butler bot added kokoro:force-run ready to pull Ready to be merged into the codebase labels Sep 14, 2023
@gbaned gbaned added kokoro:force-run ready to pull Ready to be merged into the codebase and removed ready to pull Ready to be merged into the codebase labels Sep 15, 2023
@divyashreepathihalli
Copy link
Collaborator

@pnacht do you mind opening the PR in https://github.com/keras-team/tf-keras repo instead since this repo is no longer active?

@google-ml-butler google-ml-butler bot removed the ready to pull Ready to be merged into the codebase label Sep 15, 2023
@pnacht pnacht mentioned this pull request Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Closed/Rejected
Development

Successfully merging this pull request may close these issues.

Add a dedicated file for Keras' security policy
5 participants