sjelfull/renaming-craft-plugin-repos-from-craft3-to-craft

## renaming-craft-plugin-repos-from-craft3-to-craft
1. Rename the GitHub.com repo to change `craft3-` to `craft-`
2. Pull all changes down, then duplicate `master` naming it `v1`, or `v2` or whatever
3. Push the new versioned branch to remote
4. On Github, click on Settings->Branches and change the default repo
5. On Github click on Branches from the main page, and delete the `master` branch
6. Delete `master` in your local repo
7. Search through your project and change all instances of `craft3-` to `craft-`
8. Update your `docs` URL and `changelogUrl` to point to the new repo/branch
9. Bump the version number in `composer.json` and `CHANGELOG.md`
10. Push all of the changes with your normal gitflow release cycle
11. Go to Packagist.org and submit a new package with your renamed Github URL
12. Test your auto-update web hook from Github via Settings->Integrations & Services to make sure it's auto-updating on Packagist
13. Find your old package on Packagist.org and click on Abandon Package, giving it your new package name to refer people to
14. Rename the local project dir to remove the `craft3-`, and point any GUI clients at it's new home
15. Do `git remote set-url origin https://github.com/vendor/package` from your repo's dir
16. Post an issue on https://github.com/pixelandtonic/craftcom/issues telling Brandon & co that you need your plugin updated
17. Put a link to the issue in #pluginstore to harass everyone
18. Prepare a Tweet to send out when the changes have been made on P&T's end (when the issue is closed)
19. Once the web hook has been updated on their end, go to your repo on Github and click Settings -> Webhooks and delete the one that's showing an error (you should have 2 now)
20. Have a beer

Credits to https://github.com/nystudio107
	1. Rename the GitHub.com repo to change `craft3-` to `craft-`
	2. Pull all changes down, then duplicate `master` naming it `v1`, or `v2` or whatever
	3. Push the new versioned branch to remote
	4. On Github, click on Settings->Branches and change the default repo
	5. On Github click on Branches from the main page, and delete the `master` branch
	6. Delete `master` in your local repo
	7. Search through your project and change all instances of `craft3-` to `craft-`
	8. Update your `docs` URL and `changelogUrl` to point to the new repo/branch
	9. Bump the version number in `composer.json` and `CHANGELOG.md`
	10. Push all of the changes with your normal gitflow release cycle
	11. Go to Packagist.org and submit a new package with your renamed Github URL
	12. Test your auto-update web hook from Github via Settings->Integrations & Services to make sure it's auto-updating on Packagist
	13. Find your old package on Packagist.org and click on Abandon Package, giving it your new package name to refer people to
	14. Rename the local project dir to remove the `craft3-`, and point any GUI clients at it's new home
	15. Do `git remote set-url origin https://github.com/vendor/package` from your repo's dir
	16. Post an issue on https://github.com/pixelandtonic/craftcom/issues telling Brandon & co that you need your plugin updated
	17. Put a link to the issue in #pluginstore to harass everyone
	18. Prepare a Tweet to send out when the changes have been made on P&T's end (when the issue is closed)
	19. Once the web hook has been updated on their end, go to your repo on Github and click Settings -> Webhooks and delete the one that's showing an error (you should have 2 now)
	20. Have a beer

	Credits to https://github.com/nystudio107