From 304d2be843bfdf0afc5b36f8a99a2ca22ead3035 Mon Sep 17 00:00:00 2001 From: Haacked Date: Tue, 5 Nov 2013 15:06:13 -0800 Subject: [PATCH] Add link to Octokit on MyGet --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 706e0234..06785aca 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,7 @@ When we're ready to deploy a new release, we need to do the following steps. 2. Update [`ReleaseNotes.md`](ReleaseNotes.md). Note that the format is important as we parse the version out and use that for the NuGet packages. 3. Push the branch to GitHub and create a pull request. This will kick off the MyGet build of the NuGet package with this new version. 4. Test! -5. When you're satisfied with this release, push the package from MyGet to NuGet. +5. When you're satisfied with this release, push the package [from MyGet](https://www.myget.org/feed/Packages/octokit) to NuGet. 6. Create a tag `git tag v#.#.#`. For example, to create a tag for 1.0.0 `git tag v1.0.0` 7. Accept the pull request. 8. Create a [new release](https://github.com/octokit/octokit.net/releases/new) using the tag you just created and pasting in the release notes you just wrote up