Permalink
Switch branches/tags
release-1434511043 RELEASE.2018-09-12T18-49-56Z RELEASE.2018-09-11T01-39-21Z RELEASE.2018-09-01T00-38-25Z RELEASE.2018-08-25T01-56-38Z RELEASE.2018-08-21T00-37-20Z RELEASE.2018-08-18T03-49-57Z RELEASE.2018-08-02T23-11-36Z RELEASE.2018-07-31T02-11-47Z RELEASE.2018-07-23T18-34-49Z RELEASE.2018-07-13T00-09-07Z RELEASE.2018-07-10T01-42-11Z RELEASE.2018-06-29T02-11-29Z RELEASE.2018-06-22T23-48-46Z RELEASE.2018-06-09T03-43-35Z RELEASE.2018-06-08T03-49-38Z RELEASE.2018-06-07T19-10-07Z RELEASE.2018-05-25T19-49-13Z RELEASE.2018-05-16T23-35-33Z RELEASE.2018-05-11T00-29-24Z RELEASE.2018-05-10T00-00-42Z RELEASE.2018-05-04T23-13-12Z RELEASE.2018-04-27T23-33-52Z RELEASE.2018-04-19T22-54-58Z RELEASE.2018-04-12T23-41-09Z RELEASE.2018-04-04T05-20-54Z RELEASE.2018-03-30T00-38-44Z RELEASE.2018-03-28T23-45-53Z RELEASE.2018-03-19T19-22-06Z RELEASE.2018-03-16T22-52-12Z RELEASE.2018-03-12T21-25-28Z RELEASE.2018-02-09T22-40-05Z RELEASE.2018-01-18T20-33-21Z RELEASE.2018-01-02T23-07-00Z RELEASE.2017-12-28T01-21-00Z RELEASE.2017-11-22T19-55-46Z RELEASE.2017-10-27T18-59-02Z RELEASE.2017-09-29T19-16-56Z RELEASE.2017-08-05T00-00-53Z RELEASE.2017-07-24T18-27-35Z RELEASE.2017-06-13T19-01-01Z RELEASE.2017-05-05T01-14-51Z RELEASE.2017-04-29T00-40-27Z RELEASE.2017-04-25T01-27-49Z RELEASE.2017-03-16T21-50-32Z RELEASE.2017-02-16T01-47-30Z RELEASE.2017-02-15T22-55-24Z RELEASE.2017-01-25T03-14-52Z RELEASE.2016-12-13T17-19-42Z RELEASE.2016-12-12T23-44-33Z RELEASE.2016-12-12T18-35-43Z RELEASE.2016-11-26T02-23-47Z RELEASE.2016-11-24T02-09-08Z RELEASE.2016-10-24T21-23-47Z RELEASE.2016-10-22T00-50-41Z RELEASE.2016-10-14T04-00-39Z RELEASE.2016-10-07T01-16-39Z RELEASE.2016-09-11T17-42-18Z RELEASE.2016-08-21T02-44-47Z RELEASE.2016-08-16T23-19-45Z RELEASE.2016-07-13T21-46-05Z RELEASE.2016-06-03T19-32-05Z RELEASE.2016-04-17T22-09-24Z RELEASE.2016-04-14T18-38-10Z RELEASE.2016-03-21T21-08-51Z RELEASE.2016-03-11T03-45-50Z OFFICIAL.2016-02-08T00-12-28Z
Nothing to show
Find file Copy path
72 lines (54 sloc) 3.2 KB

Minio Contribution Guide Slack Go Report Card Docker Pulls codecov

Minio community welcomes your contribution. To make the process as seamless as possible, we recommend you read this contribution guide.

Development Workflow

Start by forking the Minio GitHub repository, make changes in a branch and then send a pull request. We encourage pull requests to discuss code changes. Here are the steps in details:

Setup your Minio GitHub Repository

Fork Minio upstream source repository to your own personal repository. Copy the URL of your Minio fork (you will need it for the git clone command below).

$ mkdir -p $GOPATH/src/github.com/minio
$ cd $GOPATH/src/github.com/minio
$ git clone <paste saved URL for personal forked minio repo>
$ cd minio

Set up git remote as upstream

$ cd $GOPATH/src/github.com/minio/minio
$ git remote add upstream https://github.com/minio/minio
$ git fetch upstream
$ git merge upstream/master
...

Create your feature branch

Before making code changes, make sure you create a separate branch for these changes

$ git checkout -b my-new-feature

Test Minio server changes

After your code changes, make sure

  • To add test cases for the new code. If you have questions about how to do it, please ask on our Slack channel.
  • To run make verifiers
  • To squash your commits into a single commit. git rebase -i. It's okay to force update your pull request.
  • To run go test -race ./... and go build completes.

Commit changes

After verification, commit your changes. This is a great post on how to write useful commit messages

$ git commit -am 'Add some feature'

Push to the branch

Push your locally committed changes to the remote origin (your fork)

$ git push origin my-new-feature

Create a Pull Request

Pull requests can be created via GitHub. Refer to this document for detailed steps on how to create a pull request. After a Pull Request gets peer reviewed and approved, it will be merged.

FAQs

How does Minio manages dependencies?

Minio manages its dependencies using govendor. To add a dependency

  • Run go get foo/bar
  • Edit your code to import foo/bar
  • Run make pkg-add PKG=foo/bar from top-level directory

To remove a dependency

  • Edit your code to not import foo/bar
  • Run make pkg-remove PKG=foo/bar from top-level directory

What are the coding guidelines for Minio?

Minio is fully conformant with Golang style. Refer: Effective Go article from Golang project. If you observe offending code, please feel free to send a pull request or ping us on Slack.