From 80eadc3bcf1209a74e6c7e2747c43793a8c5335d Mon Sep 17 00:00:00 2001 From: Luke Farnell Date: Sat, 8 Apr 2017 17:11:23 -0400 Subject: [PATCH] Fixed readme.md and contributing.md --- CONTRIBUTING.md | 12 ++++++------ README.md | 6 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 882a15dfe..b4025859e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,15 +65,15 @@ following steps in order to be able to compile and test Packer. These instructio ``` 3. Download the Packer source (and its dependencies) by running `go get - github.com/mitchellh/packer`. This will download the Packer source to - `$GOPATH/src/github.com/mitchellh/packer`. + github.com/hashicorp/packer`. This will download the Packer source to + `$GOPATH/src/github.com/hashicorp/packer`. -4. When working on packer `cd $GOPATH/src/github.com/mitchellh/packer` so you +4. When working on packer `cd $GOPATH/src/github.com/hashicorp/packer` so you can run `make` and easily access other files. Run `make help` to get information about make targets. 5. Make your changes to the Packer source. You can run `make` in - `$GOPATH/src/github.com/mitchellh/packer` to run tests and build the packer + `$GOPATH/src/github.com/hashicorp/packer` to run tests and build the packer binary. Any compilation errors will be shown when the binaries are rebuilding. If you don't have `make` you can simply run `go build -o bin/packer .` from the project root. @@ -86,7 +86,7 @@ following steps in order to be able to compile and test Packer. These instructio ### Opening an Pull Request -When you are ready to open a pull-request, you will need to [fork packer](https://github.com/mitchellh/packer#fork-destination-box), push your changes to your fork, and then open a pull-request. +When you are ready to open a pull-request, you will need to [fork packer](https://github.com/hashicorp/packer#fork-destination-box), push your changes to your fork, and then open a pull-request. For example, my github username is `cbednarski` so I would do the following: @@ -104,7 +104,7 @@ From there, open your fork in your browser to open a new pull-request. The easiest way to work on a fork is to set it as a remote of the packer project. After following the steps in "Setting up Go to work on Packer": -1. Navigate to $GOPATH/src/github.com/mitchellh/packer +1. Navigate to $GOPATH/src/github.com/hashicorp/packer 2. Add the remote `git remote add `. For example `git remote add mwhooker https://github.com/mwhooker/packer.git`. 3. Checkout a feature branch: `git checkout -b new-feature` 4. Make changes diff --git a/README.md b/README.md index 3f11bb82d..b61dd6d8b 100644 --- a/README.md +++ b/README.md @@ -5,8 +5,8 @@ [![GoDoc][godoc-badge]][godoc] [![GoReportCard][report-badge]][report] -[travis-badge]: https://travis-ci.org/mitchellh/packer.svg?branch=master -[travis]: https://travis-ci.org/mitchellh/packer +[travis-badge]: https://travis-ci.org/hashicorp/packer.svg?branch=master +[travis]: https://travis-ci.org/hashicorp/packer [appveyor-badge]: https://ci.appveyor.com/api/projects/status/github/mitchellh/packer?branch=master&svg=true [appveyor]: https://ci.appveyor.com/project/hashicorp/packer [godoc-badge]: https://godoc.org/github.com/mitchellh/packer?status.svg @@ -49,7 +49,7 @@ The images that Packer creates can easily be turned into ## Quick Start Download and install packages and dependencies ``` -go get github.com/mitchellh/packer +go get github.com/hashicorp/packer ``` **Note:** There is a great