| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Useful for testing local Dockerfile changes that have not been pushed yet.
|
| |
|
|
|
|
|
|
|
|
| |
act(https://github.com/nektos/act) is used to build github workflow locally.
When running `act -j build` in local host, it reports:
exec failed: unable to start container process: exec: "node": executable file
not found in $PATH: unknown.
Adding nodejs package can fix the build error.
Updated docs with act usage too.
|
| |
|
|
| |
Fix a typo in the section of "Using syz-env": expacted to expected.
|
| |
|
|
| |
Fix various typos within the documentation directory.
|
| |
|
|
|
|
| |
Updated documentation regarding source code checkout from the legacy gopath
mode 'go get' to 'git clone'.
Fixes #2828
|
| | |
|
| |
|
|
| |
Add some general contribution guidelines.
|
| |
|
|
|
|
| |
Paths like SOURCEDIR must be absolute as they're being used as volume
paths given to Docker and will be interpreted as Docker volume names if
not absolute paths.
|
| |
|
|
|
| |
Some users don't have access to the gcr.io registry.
Mirror images on github as well.
|
| |
|
|
|
| |
Check PR commit subjects for the standard format we use "pkg/name: description of the change".
Check PR commit bodies for at most 120 characters.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
syz-env provides a canned dev environment with all tools necessary
(Go, gcc, clang-format, etc) for development/testing in a form
of a Docker image. Example use:
$ syz-env make presubmit
$ syz-env make extract SOURCEDIR=~/linux
Update #1699
|
| | |
|
| | |
|
| |
|
|
| |
Also update go version requirement to 1.13.
|
| |
|
|
|
|
|
|
| |
Since we don't don't have auto-generated files checked-in,
go get fails to parse packages.
go get only prog package without building,
this will checkout the whole repo anyway
and that's the only thing we need.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checking in the generated descriptions files makes few things simpler,
but causes pain for pull requests: (1) PRs that touch descriptions
_always_ conflict, (2) PRs are large and harder to review,
(3) people sometimes forget to add auto-generated files.
The proposed way does not require us to hardcode lots of dependencies
in the Makefile (which is nice) and seem to work.
Let's see how it works.
The main contributor-visible consequence is that the auto-generated
files do not need to be checked-in now.
Credit for figuring the Makefile magic goes to @melver.
Fixes #1291
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Add suggestions for running make install_prerequisites.
|
| |
|
|
|
|
|
|
| |
Differences in code formatting between Go versions cause constant
problems for us (https://github.com/golang/go/issues/25161).
Currently we support 1.9 and 1.10. Switch to newer 1.11 and 1.12.
Fixes #1013
|
| |
|
|
|
|
| |
Extend doc on descriptions, const generation process,
add more links to internals, explain programs, etc.
Clarify that all generated files are checked in.
|
| |
|
|
|
| |
The current step creates a local branch from the default origin, which is
probably not my-origin in the instruction.
|
| |
|
| |
Clarify commit description guidelines.
|
| |
|
| |
fix formatting
|
| |
|
|
| |
Details how to run tests and how to work around gofmt bug.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
