The Dangerous Convenience of Implicit Ownership
Authorization systems often become complicated one convenience at a time. Everlock ran into a good example of this while working on repository permissions. The original rule sounded harmless:
Documentation
Tag: permissions
The repository web UI
The host that serves [git over HTTP](/docs/git/http) also serves a browser surface over every hosted repository — one interface for the instance, not one per repository. It comes up with the backend:
Can You Accept a Git Pull Request Without Giving Someone Write Access?
Pull requests look simple when a forge is doing the work for you. A contributor creates an account, forks a repository, pushes a branch, and clicks a button. The forge connects all of those pieces and
Permissions reference — backends, paths, and roles
This is the complete catalogue of what you can grant. Everything Everlock controls is reachable through **one** grant model: a `role` attached to a subject (user or group) on an `access path`. There i