Merge pull request #75 from docker/move-dockerorg

Move to Docker org

.github/CONTRIBUTING.md

@@ -7,14 +7,14 @@ to the public under the [project's open source license](LICENSE).
 
 ## Submitting a pull request
 
-1. [Fork](https://github.com/crazy-max/ghaction-docker-meta/fork) and clone the repository
+1. [Fork](https://github.com/docker/metadata-action/fork) and clone the repository
 2. Configure and install the dependencies: `yarn install`
 3. Create a new branch: `git checkout -b my-branch-name`
 4. Make your changes
 5. Make sure the tests pass: `docker buildx bake test`
 6. Format code and build javascript artifacts: `docker buildx bake pre-checkin`
 7. Validate all code has correctly formatted and built: `docker buildx bake validate`
-8. Push to your fork and [submit a pull request](https://github.com/crazy-max/ghaction-docker-meta/compare)
+8. Push to your fork and [submit a pull request](https://github.com/docker/metadata-action/compare)
 9. Pat your self on the back and wait for your pull request to be reviewed and merged.
 
 Here are a few things you can do that will increase the likelihood of your pull request being accepted:

.github/ISSUE_TEMPLATE/bug_report.md

@@ -13,11 +13,11 @@ about: Create a report to help us improve
 
 #### Expected behaviour
 
-> Tell me what should happen
+> Tell us what should happen
 
 #### Actual behaviour
 
-> Tell me what happens instead
+> Tell us what happens instead
 
 ### Configuration
 

.github/SUPPORT.md

@@ -1,10 +1,13 @@
-# Support [![](https://isitmaintained.com/badge/resolution/crazy-max/ghaction-docker-meta.svg)](https://isitmaintained.com/project/crazy-max/ghaction-docker-meta)
+# Support [![](https://isitmaintained.com/badge/resolution/docker/metadata-action.svg)](https://isitmaintained.com/project/docker/metadata-action)
 
 ## Reporting an issue
 
-Please do a search in [open issues](https://github.com/crazy-max/ghaction-docker-meta/issues?utf8=%E2%9C%93&q=) to see if the issue or feature request has already been filed.
+Please do a search in [open issues](https://github.com/docker/metadata-action/issues?utf8=%E2%9C%93&q=) to see if the
+issue or feature request has already been filed.
 
-If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment.
+If you find your issue already exists, make relevant comments and add your
+[reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place
+of a "+1" comment.
 
 :+1: - upvote
 
@@ -21,9 +24,9 @@ File a single issue per problem and feature request.
 
 The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.
 
-You are now ready to [create a new issue](https://github.com/crazy-max/ghaction-docker-meta/issues/new/choose)!
+You are now ready to [create a new issue](https://github.com/docker/metadata-action/issues/new/choose)!
 
 ## Closure policy
 
 * Issues that don't have the information requested above (when applicable) will be closed immediately and the poster directed to the support guidelines.
-* Issues that go a week without a response from original poster are subject to closure at my discretion.
+* Issues that go a week without a response from original poster are subject to closure at our discretion.