How to make file repositories private
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Container distributions have a private setting, but as far as I know there's not a similar setting for other repository types. I have a file repository that I would like to deny all access (even view) to by default so that I can give users permissions as needed, but it's not clear to me how to do that. Would that be done via a content guard? Are there any docs (I didn't see any, but maybe I'm missing something) that provide guidance on how to disable or work around the default read-all behavior of non-container distributions?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing documentation for private container distributions and content guards first. Determine whether non-container file repositories can deny default read access and how permissions can be granted selectively; document the supported configuration or any workaround, including the relevant limitations.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100