Fixup contributing

Author: sgoedecke

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing
 
-[fork]: https://github.com/actions/ai-moderator/fork
-[pr]: https://github.com/actions/ai-moderator/compare
+[fork]: https://github.com/github/ai-moderator/fork
+[pr]: https://github.com/github/ai-moderator/compare
 [code-of-conduct]: CODE_OF_CONDUCT.md
 
 Hi there! We're thrilled that you'd like to contribute to this project. Your
@@ -18,9 +18,9 @@ by its terms.
 ## Found a bug?
 
 - **Ensure the bug was not already reported** by searching on GitHub under
-  [Issues](https://github.com/actions/ai-moderator/issues).
+  [Issues](https://github.com/github/ai-moderator/issues).
 - If you're unable to find an open issue addressing the problem,
-  [open a new one](https://github.com/actions/ai-moderator/issues/new). Be sure
+  [open a new one](https://github.com/github/ai-moderator/issues/new). Be sure
   to include a **title and clear description**, as much relevant information as
   possible, and a **code sample** or a **reproducible test case** demonstrating
   the expected behavior that is not occurring.
@@ -66,24 +66,11 @@ All the concepts from
 [the actions/toolkit release docs](https://github.com/actions/toolkit/blob/main/docs/action-versioning.md)
 apply. Please read that first!
 
-Once the changes are merged into main, a repository maintainer should:
-
-1. Bump the package version by running
-   [`npm version [major|minor|patch]`](https://docs.npmjs.com/cli/v7/commands/npm-version).
-   We adhere to [SemVer 2.0](https://semver.org/spec/v2.0.0.html) to the best of
-   our ability. Commit the changes to `package.json` and `package-lock.json` and
-   push them to main.
-1. [Draft a new release](https://github.com/actions/ai-moderator/releases/new)
-   pointing to the ref of the version bump you just made. Publish the release to
-   the marketplace when complete.
-1. Finally: update the corresponding "major tag" (v1, v2, v3, etc) to point to
-   the specific ref of the release you just made. For example, if we just
-   released `v1.1.0`, we would rewrite the `v1` tag like this:
-
-```bash
-git tag -fa v1 v1.1.0 -m "Update v1 tag to point to v1.1.0"
-git push origin v1 --force
-```
+Once the changes are merged into main, a repository maintainer should
+[draft a new release](https://github.com/github/ai-moderator/releases/new)
+pointing to the ref of the version bump you just made. Publish the release to
+the marketplace when complete. The corresponding major tag (v1, v2, etc) should
+be automatically updated.
 
 ## Licensed
 
@@ -104,5 +91,3 @@ of dependencies.
 - [Writing good commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
 
 Thanks! :heart: :heart: :heart:
-
-GitHub Actions Team :octocat: