Contributing to Docker Guidline

issues dabases

There are two groups. Docker-user is for people using Docker containers. The docker-dev group is fore contributors and other people contributing to the Docker project.

Docker user forum

Docker dev forum

stackoverflow about docker

test suite

It can take approximate one hour to run all the tests

Write clean code. Universally formatted code promotes ease of writing, reading, and maintenance. Always run gofmt -s -w file.go on each changed file before committing your changes. Most editors have plug-ins that do this automatically.

Git tip: If your PR no longer merges cleanly, use rebase master in your feature branch to update your pull request rather than merge master.

Before you make a pull request, squash your commits into logical units of work using git rebase -i and git push -f. A logical unit of work is a consistent set of patches that should be reviewed together: for example, upgrading the version of a vendored dependency and taking advantage of its now available new feature constitute two separate units of work. Implementing a new function and calling it in another file constitute a single logical unit of work. The very high majority of submissions should have a single commit, so if in doubt: squash down to one.

Q: git rebase -i and git push

MainTainers list

Golang test