| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Only the owner or a maintainer of the project can remove a review.
Removing a review also removes the git branch.
Only reviews that are either draft or dropped can be removed.
|
|
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.
|
|
Want to support any authentication for the git server, so use git
commiter as username for creating reviews instead of the local user
that logged in to git.
Also verify that pushed commits has a valid author in pre-receive.
This is tricky as pre-receive must do this check in the hook, because
pre-receive runs when before the objects are pushed so the server
can't read the commits, the hook must do this.
|
|
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.
|
|
Apperntly, cargo sqlx prepare --all is not enough, we need:
cargo sqlx prepare -- --all-targets --all-features
|
|
Forgot a sqlx query
|
|
User: username must be unique, use as primary key and drop id.
|
|
Avoid having to have an active server and a migrated database
to be able to build.
Instead, when a new query is added or the database updated,
cargo sqlx prepare needs to be run again, then with a running
server and an active database. But only then.
|
