Replace 'starknet-community-libs' with 'starknet-io' everywhere

github.com/starknet-community-libs is now github.com/starknet-io

.github/ISSUE_TEMPLATE/config.yml

@@ -2,5 +2,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: SNIPs Community Support
-    url: https://github.com/starknet-community-libs/SNIPs/discussions
+    url: https://github.com/starknet-io/SNIPs/discussions
     about: Please ask and answer questions here.

README.md

@@ -8,11 +8,11 @@
         <img src="https://img.shields.io/badge/Twitter-1DA1F2?style=for-the-badge&logo=twitter&logoColor=white">
     </a>
       <br />
-  <a href="https://github.com/starknet-community-libs/SNIPs/issues/new?assignees=&labels=bug&template=01_BUG_REPORT.md&title=bug%3A+">Report a Bug</a>
+  <a href="https://github.com/starknet-io/SNIPs/issues/new?assignees=&labels=bug&template=01_BUG_REPORT.md&title=bug%3A+">Report a Bug</a>
   -
-  <a href="https://github.com/starknet-community-libs/SNIPs/issues/new?assignees=&labels=enhancement&template=02_FEATURE_REQUEST.md&title=feat%3A+">Request a Feature</a>
+  <a href="https://github.com/starknet-io/SNIPs/issues/new?assignees=&labels=enhancement&template=02_FEATURE_REQUEST.md&title=feat%3A+">Request a Feature</a>
   -
-  <a href="https://github.com/starknet-community-libs/SNIPs/discussions">Ask a Question</a>       
+  <a href="https://github.com/starknet-io/SNIPs/discussions">Ask a Question</a>       
   </p>
 
   <h3 align="center">StarkNet Improvement Proposal repository.</h3>
@@ -21,9 +21,9 @@
 <div align="center">
 <br />
 
-[![Project license](https://img.shields.io/github/license/starknet-community-libs/SNIPs.svg?style=flat-square)](LICENSE)
-[![Pull Requests welcome](https://img.shields.io/badge/PRs-welcome-ff69b4.svg?style=flat-square)](https://github.com/starknet-community-libs/SNIPs/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
-[![code with love by StarkNet community](https://img.shields.io/badge/%3C%2F%3E%20with%20%E2%99%A5%20by-StarkNet%20Community-ff1414.svg?style=flat-square)](https://github.com/starknet-community-libs)
+[![Project license](https://img.shields.io/github/license/starknet-io/SNIPs.svg?style=flat-square)](LICENSE)
+[![Pull Requests welcome](https://img.shields.io/badge/PRs-welcome-ff69b4.svg?style=flat-square)](https://github.com/starknet-io/SNIPs/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
+[![code with love by StarkNet community](https://img.shields.io/badge/%3C%2F%3E%20with%20%E2%99%A5%20by-StarkNet%20Community-ff1414.svg?style=flat-square)](https://github.com/starknet-io)
 
 </div>
 
@@ -56,7 +56,7 @@ Here is the process that a contributor should follow:
 1. Review [SNIP-1](./SNIPS/snip-1.md).
 2. Fork the repository by clicking "Fork" in the top right.
 3. Add your SNIP to your fork of the repository. There is a [template SNIP here](./SNIPS/snip-template.md).
-4. Submit a Pull Request to [SNIPs repository](https://github.com/starknet-community-libs/SNIPs)
+4. Submit a Pull Request to [SNIPs repository](https://github.com/starknet-io/SNIPs)
 
 Your first PR should be a first draft of the final SNIP. It must meet the formatting criteria enforced by the build (largely, correct metadata in the header). An editor will manually review the first PR for a new SNIP and assign it a number before merging it. Make sure you include a `discussions-to` header with the URL to a discussion forum or open GitHub issue where people can discuss the SNIP as a whole.
 
@@ -83,7 +83,7 @@ Reach out to the maintainer at one of the following places:
 
 If you want to say **thank you** or/and support active development of SNIPs:
 
-- Add a [GitHub Star](https://github.com/starknet-community-libs/SNIPs) to the project.
+- Add a [GitHub Star](https://github.com/starknet-io/SNIPs) to the project.
 - Tweet about the SNIPs.
 - Write interesting articles about the project on [Dev.to](https://dev.to/), [Medium](https://medium.com/) or your personal blog.
 
@@ -97,7 +97,7 @@ Please read [our contribution guidelines](docs/CONTRIBUTING.md), and thank you f
 
 ## Authors & contributors
 
-For a full list of all authors and contributors, see [the contributors page](https://github.com/starknet-community-libs/SNIPs/contributors).
+For a full list of all authors and contributors, see [the contributors page](https://github.com/starknet-io/SNIPs/contributors).
 
 ## Security
 

docs/CODE_OF_CONDUCT.md

@@ -34,7 +34,7 @@ This Code of Conduct applies within all project spaces, and it also applies when
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project maintainer using any of the [private contact addresses](https://github.com/starknet-community-libs/SNIPs#support). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project maintainer using any of the [private contact addresses](https://github.com/starknet-io/SNIPs#support). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 

docs/CONTRIBUTING.md

@@ -14,14 +14,14 @@ To set up a development environment, please follow these steps:
 1. Clone the repo
 
    ```sh
-   git clone https://github.com/starknet-community-libs/SNIPs
+   git clone https://github.com/starknet-io/SNIPs
    ```
 
 2. TODO
 
 ## Issues and feature requests
 
-You've found a bug in the source code, a mistake in the documentation or maybe you'd like a new feature?Take a look at [GitHub Discussions](https://github.com/starknet-community-libs/SNIPs/discussions) to see if it's already being discussed. You can help us by [submitting an issue on GitHub](https://github.com/starknet-community-libs/SNIPs/issues). Before you create an issue, make sure to search the issue archive -- your issue may have already been addressed!
+You've found a bug in the source code, a mistake in the documentation or maybe you'd like a new feature?Take a look at [GitHub Discussions](https://github.com/starknet-io/SNIPs/discussions) to see if it's already being discussed. You can help us by [submitting an issue on GitHub](https://github.com/starknet-io/SNIPs/issues). Before you create an issue, make sure to search the issue archive -- your issue may have already been addressed!
 
 Please try to create bug reports that are:
 
@@ -35,10 +35,10 @@ Please try to create bug reports that are:
 ### How to submit a Pull Request
 
 1. Search our repository for open or closed
-   [Pull Requests](https://github.com/starknet-community-libs/SNIPs/pulls)
+   [Pull Requests](https://github.com/starknet-io/SNIPs/pulls)
    that relate to your submission. You don't want to duplicate effort.
 2. Fork the project
 3. Create your feature branch (`git checkout -b feat/amazing_feature`)
 4. Commit your changes (`git commit -m 'feat: add amazing_feature'`)
 5. Push to the branch (`git push origin feat/amazing_feature`)
-6. [Open a Pull Request](https://github.com/starknet-community-libs/SNIPs/compare?expand=1)
+6. [Open a Pull Request](https://github.com/starknet-io/SNIPs/compare?expand=1)

docs/SECURITY.md

@@ -4,7 +4,7 @@
 
 If there are any vulnerabilities in **SNIPs**, don't hesitate to _report them_.
 
-1. Use any of the [private contact addresses](https://github.com/starknet-community-libs/SNIPs#support).
+1. Use any of the [private contact addresses](https://github.com/starknet-io/SNIPs#support).
 2. Describe the vulnerability.
 
    If you have a fix, that is most welcome -- please attach or summarize it in your message!