Conversation
Create a security policy for submitting security vulnerabilities to the Jekyll team.
ashmaroli
reviewed
Sep 26, 2021
Co-authored-by: Ashwin Maroli <ashmaroli@users.noreply.github.com>
Closed
Co-authored-by: Ashwin Maroli <ashmaroli@users.noreply.github.com>
ashmaroli
approved these changes
Oct 10, 2021
Member
|
@parkr I have some additional comments that you may choose to consider implementing as part of this PR or defer for a future one:
|
Member
|
ping @mattr- |
mattr-
approved these changes
Dec 16, 2021
Member
|
Thank you @parkr |
jekyllbot
added a commit
that referenced
this pull request
Dec 16, 2021
github-actions bot
pushed a commit
that referenced
this pull request
Dec 16, 2021
Parker Moore: Add Security Policy document (#8823) Merge pull request 8823
Member
Author
Absolutely! This is a great idea. Feel free to PR it since it was your idea.
We can try |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a 🔦 documentation change.
Summary
Create a security policy for submitting security vulnerabilities to the Jekyll team.
Context
I'm going to continue maintaining the Jekyll v3.9.x branch for GitHub Pages for a while. One thing that would be nice to have is a security policy so that we can receive vulnerabilities directly. I've hand-written this policy. Feel free to make suggestions.
Fixes #8755.