| Age | Commit message (Collapse) | Author |
|
But also add /review endpoint that takes an id. So you can get
review data with either the reviewid or the branchname.
|
|
Next step is to generate authorized_keys files for git server
based on keys.
|
|
Pushing a commit to a new branch creates a review.
Each project has its own git directory, with githooks installed
that talkes with server process via unix sockets.
|
|
Non existent projects, users and such.
|
|
User: username must be unique, use as primary key and drop id.
|
|
Preparing for git connection.
|
|
Also add /users endpoint.
|
|
While doing that I realized I had forgotten to declare maintainers
for projects. Also added default roles and changed so that review_users
only contains overrides, so that changes to the project users is
instantly applied to all reviews (unless there is an override).
|
|
|
|
The actual authentication is still fake.
|
|
|
|
|
|
|