Updating some references from mitchellh to hashicorp

website/source/docs/builders/docker.html.md

@@ -1,4 +1,4 @@
----
+hashicorp---
 description: |
     The docker Packer builder builds Docker images using Docker. The builder
     starts a Docker container, runs provisioners within this container, then
@@ -227,7 +227,7 @@ post-processors that are treated as as single pipeline, see
     [
       {
         "type": "docker-import",
-        "repository": "mitchellh/packer",
+        "repository": "hashicorp/packer",
         "tag": "0.7"
       },
       "docker-push"
@@ -266,7 +266,7 @@ which tags and pushes an image. This is accomplished using a sequence definition
     [
       {
         "type": "docker-tag",
-        "repository": "mitchellh/packer",
+        "repository": "hashicorp/packer",
         "tag": "0.7"
       },
       "docker-push"
@@ -291,7 +291,7 @@ nearly-identical sequence definitions, as demonstrated by the example below:
     [
       {
         "type": "docker-tag",
-        "repository": "mitchellh/packer",
+        "repository": "hashicorp/packer",
         "tag": "0.7"
       },
       "docker-push"

website/source/docs/extending/custom-builders.html.md

@@ -115,7 +115,7 @@ The only part of an artifact that may be confusing is the `BuilderId` method.
 This method must return an absolutely unique ID for the builder. In general, I
 follow the practice of making the ID contain my GitHub username and then the
 platform it is building for. For example, the builder ID of the VMware builder
-is "mitchellh.vmware" or something similar.
+is "hashicorp.vmware" or something similar.
 
 Post-processors use the builder ID value in order to make some assumptions about
 the artifact results, so it is important it never changes.

website/source/docs/extending/plugins.html.md

@@ -114,7 +114,7 @@ the following two packages, you're encouraged to use whatever packages you want.
 Because plugins are their own processes, there is no danger of colliding
 dependencies.
 
--   `github.com/mitchellh/packer` - Contains all the interfaces that you have to
+-   `github.com/hashicorp/packer` - Contains all the interfaces that you have to
     implement for any given plugin.
 
 -   `github.com/hashicorp/packer/packer/plugin` - Contains the code to serve

website/source/docs/install/index.html.md

@@ -41,8 +41,8 @@ as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
 1.  Clone the Packer repository from GitHub into your `GOPATH`:
 
     ``` shell
-    $ mkdir -p $GOPATH/src/github.com/mitchellh && cd $!
-    $ git clone https://github.com/mitchellh/packer.git
+    $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $!
+    $ git clone https://github.com/hashicorp/packer.git
     $ cd packer
     ```
 

website/source/docs/post-processors/docker-import.html.md

@@ -36,13 +36,13 @@ An example is shown below, showing only the post-processor configuration:
 ``` json
 {
   "type": "docker-import",
-  "repository": "mitchellh/packer",
+  "repository": "hashicorp/packer",
   "tag": "0.7"
 }
 ```
 
 This example would take the image created by the Docker builder and import it
-into the local Docker process with a name of `mitchellh/packer:0.7`.
+into the local Docker process with a name of `hashicorp/packer:0.7`.
 
 Following this, you can use the
 [docker-push](/docs/post-processors/docker-push.html) post-processor to push it

website/source/docs/post-processors/docker-tag.html.md

@@ -44,13 +44,13 @@ An example is shown below, showing only the post-processor configuration:
 ``` json
 {
   "type": "docker-tag",
-  "repository": "mitchellh/packer",
+  "repository": "hashicorp/packer",
   "tag": "0.7"
 }
 ```
 
 This example would take the image created by the Docker builder and tag it into
-the local Docker process with a name of `mitchellh/packer:0.7`.
+the local Docker process with a name of `hashicorp/packer:0.7`.
 
 Following this, you can use the
 [docker-push](/docs/post-processors/docker-push.html) post-processor to push it

website/source/intro/getting-started/next.html.md

@@ -26,5 +26,5 @@ overview](https://atlas.hashicorp.com/help/intro/getting-started).
 
 As you use Packer more, please voice your comments and concerns on the [mailing
 list or IRC](/community.html). Additionally, Packer is [open
-source](https://github.com/mitchellh/packer) so please contribute if you'd like
+source](https://github.com/hashicorp/packer) so please contribute if you'd like
 to. Contributions are very welcome.

website/source/layouts/_sidebar.erb

@@ -22,7 +22,7 @@
       </a>
     </li>
     <li>
-      <a href="https://github.com/mitchellh/packer">
+      <a href="https://github.com/hashicorp/packer">
         <%= inline_svg "github.svg" %> GitHub
       </a>
     </li>

website/source/layouts/layout.erb

@@ -82,7 +82,7 @@
                     </a>
                   </li>
                   <li>
-                    <a href="https://github.com/mitchellh/packer">
+                    <a href="https://github.com/hashicorp/packer">
                       <%= inline_svg "github.svg" %> GitHub
                     </a>
                   </li>
@@ -139,7 +139,7 @@
         "url": "https://www.packer.io",
         "logo": "<%= File.join(base_url, image_path("logo-hashicorp.svg")) %>",
         "sameAs": [
-          "https://github.com/mitchellh/packer"
+          "https://github.com/hashicorp/packer"
         ]
       }
     </script>

website/source/security.html.erb

@@ -28,6 +28,6 @@ description: |-
 
 <p>
   If you are not reporting a security sensitive vulnerability, please open
-  an issue on the <a href="https://github.com/mitchellh/packer">Packer
+  an issue on the <a href="https://github.com/hashicorp/packer">Packer
   GitHub repository</a>.
 </p>