This repository was archived by the owner on Sep 20, 2023. It is now read-only.
Security FAQ #2069
Merged
Security FAQ #2069
Conversation
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.
4 participants
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 pull request addresses #2060 by adding a security FAQ document that answers questions about how GitHawk handles its privileged access to private GitHub user data. This document should be made accessible on githawk.com - it doesn't necessarily need to live in this repo.
I am not a regular contributor to GitHawk, so my answers to the questions in the FAQ are best guesses based on the very small amount of information I have about the project's internals. Someone familiar with the actual answers to these questions should make comments on this pull request correcting or improving my answers.