This repo contains a command line tool for performing code reviews on git repositories.
Assuming you have the Go tools installed, run the following command:
go get github.com/google/git-appraise/git-appraise
Then, either make sure that ${GOPATH}/bin is in your PATH, or explicitly add the "appraise" git alias by running the following command.
git config --global alias.appraise "!${GOPATH}/bin/git-appraise"
This tool expects to run in an environment with the following attributes:
- The git command line tool is installed, and included in the PATH.
- The tool is run from within a git repo.
- The git command line tool is configured with the credentials it needs to push to and pull from the remote repos.
Requesting a code review:
git appraise request
Pushing code reviews to a remote:
git appraise push [<remote>]
Pulling code reviews from a remote:
git appraise pull [<remote>]
Listing open code reviews:
git appraise list
Showing the status of the current review, including comments:
git appraise show
Commenting on a review:
git appraise comment -m "<message>" [<file> [<line>]]
Accepting the changes in a review:
git appraise accept [-m "<message>"]
Submitting a review:
git appraise submit [--merge | --rebase]
The code review data is stored in git-notes, using the formats described below. Each item stored is written as a single line of JSON, and is written with at most one such item per line. This allows the git notes to be automatically merged using the "cat_sort_uniq" strategy.
Since these notes are not in a human-friendly form, all of the refs used to track them start with the prefix "refs/notes/devtools". This helps make it clear that these are meant to be read and written by automated tools.
When a field named "v" appears in one of these notes, it is used to denote the version of the metadata format being used. If that field is missing, then it defaults to the value 0, which corresponds to this initial verison of the formats.
Code review requests are stored in the "refs/notes/devtools/reviews" ref, and annotate the first revision in a review. They must conform to the following schema.
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"timestamp": {
"type": "string"
},
"reviewRef": {
"id": "reviewRef",
"type": "string"
},
"targetRef": {
"id": "targetRef",
"type": "string"
},
"requester": {
"type": "string"
},
"reviewers": {
"type": "array",
"items": {
"type": "string"
}
},
"description": {
"type": "string"
},
"v": {
"type": "integer",
"default": 0,
"enum": [
null,
0
]
}
},
"required": [
"targetRef"
]
}
The "reviewRef" field is used to specify a git ref that tracks the current revision under review, and the "targetRef" field is used to specify the git ref that should be updated once the review is approved.
Continuous integration build and test results are stored in the "refs/notes/devtools/ci" ref, and annotate the revision that was built and tested. They must conform to the following schema.
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"timestamp": {
"type": "string"
},
"url": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
null,
"success",
"failure"
]
},
"agent": {
"type": "string"
},
"v": {
"type": "integer",
"default": 0,
"enum": [
null,
0
]
}
},
}
The "status" field is for the final status of a build or test. The "agent" field is a free-form string that identifies the build and test runner.
Robot comments are comments generated by static analysis tools. These are stored in the "refs/notes/devtools/analyses" ref, and annotate the revision. They must conform to the following schema.
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"timestamp": {
"type": "string"
},
"url": {
"type": "string"
},
"v": {
"type": "integer",
"default": 0,
"enum": [
null,
0
]
}
},
}
The "url" field should point to a publicly readable file, which contains JSON formatted analysis results. Those results should conform to the following schema, which is taken from the Note protocol buffer message defined here.
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"location": {
"type": "object",
"properties": {
"path": {
"type": "string"
},
"range": {
"type": "object",
"properties": {
"startLine": {
"type": "integer"
}
}
}
}
},
"category": {
"type": "string"
},
"description": {
"id": "description",
"type": "string"
}
},
"required": [
"description"
]
}
Review comments are comments that were written by a person rather than by a machine. These are stored in the "refs/notes/devtools/discuss" ref, and annotate the first revision in the review. They must conform to the following schema.
{
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"timestamp": {
"type": "string"
},
"author": {
"type": "string"
},
"parent": {
"type": "string"
},
"location": {
"type": "object",
"properties": {
"commit": {
"type": "string"
},
"path": {
"type": "string"
},
"range": {
"type": "object",
"properties": {
"startLine": {
"type": "integer"
}
}
}
}
},
"description": {
"type": "string"
},
"resolved": {
"type": "boolean"
},
"v": {
"type": "integer",
"default": 0,
"enum": [
null,
0
]
}
}
}
When the parent is specified, it must be the SHA1 hash of another comment on the same revision, and it means this comment is a reply to that comment.
The timestamp field represents the number of seconds since the Unix epoch, and is formatted as a 10 digit decimal number with zero padding. It should be the first field written, so that the lexicographical ordering of comments matches their chronological ordering.