chore: rename ignite-hq to ignite (#2605)

* chore: change repository URL username to "ignite" * chore: change paths and strings from "ignite-hq" to "ignite" * chore: change firebase settings to use "ignite" for project and target * chore: change goreleaser to use the new ignite repository name * chore: fix ignite repository URL in Gitpod readme * chore: rename ignitehq to ignite in test file * Update ignite/templates/app/stargate/go.mod.plush * Update docs/docs/guide/03-blog/02-connect-blockchain.md * Update ignite/templates/app/stargate/go.mod.plush * Update docs/docs/guide/03-blog/02-connect-blockchain.md * Update docs/docs/guide/03-blog/02-connect-blockchain.md * Update ignite/templates/app/stargate/go.mod.plush * chore: gh actions to ignite new repo * chore: change documentation to use the right Docker image tag Co-authored-by: İlker G. Öztürk <[email protected]> Co-authored-by: Thomas Bruyelle <[email protected]>
ignite · Jun 23, 2022 · d6c6667 · d6c6667
1 parent ae7e2e0
commit d6c6667
Show file tree

Hide file tree

Showing 285 changed files with 863 additions and 863 deletions.
diff --git a/.firebaserc b/.firebaserc
@@ -1,14 +1,14 @@
 {
   "projects": {
-    "default": "ignite-hq"
+    "default": "ignite"
   },
   "targets": {
-    "ignite-hq": {
+    "ignite": {
       "hosting": {
         "docs.ignite.com": [
           "ignite-go-docs"
         ]
       }
     }
   }
-}
+}
diff --git a/.github/workflows/docs-deploy-preview.yml b/.github/workflows/docs-deploy-preview.yml
@@ -41,4 +41,4 @@ jobs:
           firebaseServiceAccount: "${{ secrets.FIREBASE_SERVICE_ACCOUNT_IGNITE_HQ }}"
           expires: 7d
           target: docs.ignite.com
-          projectId: ignite-hq
+          projectId: ignite
diff --git a/.github/workflows/docs-deploy.yml b/.github/workflows/docs-deploy.yml
@@ -49,4 +49,4 @@ jobs:
           firebaseServiceAccount: "${{ secrets.FIREBASE_SERVICE_ACCOUNT_IGNITE_HQ }}"
           channelId: live
           target: docs.ignite.com
-          projectId: ignite-hq
+          projectId: ignite
diff --git a/.github/workflows/release-binary.yml b/.github/workflows/release-binary.yml
@@ -8,7 +8,7 @@ jobs:
   binary:
     runs-on: ubuntu-latest
     env:
-      working-directory: go/src/github.com/ignite-hq/cli 
+      working-directory: go/src/github.com/ignite/cli
 
     steps:
       - name: Set up Go

diff --git a/.github/workflows/release-nightly.yml b/.github/workflows/release-nightly.yml
@@ -17,7 +17,7 @@ jobs:
     runs-on: ubuntu-latest
     needs: [ consecutiveness ]
     env:
-      working-directory: go/src/github.com/ignite-hq/cli
+      working-directory: go/src/github.com/ignite/cli
 
     steps:
       - uses: actions/checkout@v2

diff --git a/.gitpod/readme.md b/.gitpod/readme.md
@@ -32,7 +32,7 @@ where:
 
 📚 [Cosmos SDK Documentation](https://docs.cosmos.network): Learn about the framework for building application-specific blockchains.
 
-⭐️ [Ignite CLI on Github](https://github.com/ignite-hq/cli): Submit an issue or contribute to the source code.
+⭐️ [Ignite CLI on Github](https://github.com/ignite/cli): Submit an issue or contribute to the source code.
 
 ## Ignite CLI features
 

diff --git a/.goreleaser.nightly.yml b/.goreleaser.nightly.yml
@@ -2,7 +2,7 @@ project_name: ignite
 builds:
   - main: ./ignite/cmd/ignite
     ldflags:
-      - -s -w -X github.com/ignite-hq/cli/ignite/version.Version={{.Tag}} -X github.com/ignite-hq/cli/ignite/version.Date={{.Date}} -X github.com/ignite-hq/cli/ignite/version.Head={{.FullCommit}}
+      - -s -w -X github.com/ignite/cli/ignite/version.Version={{.Tag}} -X github.com/ignite/cli/ignite/version.Date={{.Date}} -X github.com/ignite/cli/ignite/version.Head={{.FullCommit}}
     goos:
       - linux
       - darwin

diff --git a/.goreleaser.yml b/.goreleaser.yml
@@ -2,7 +2,7 @@ project_name: ignite
 builds:
   - main: ./ignite/cmd/ignite
     ldflags:
-      - -s -w -X github.com/ignite-hq/cli/ignite/version.Version={{.Tag}} -X github.com/ignite-hq/cli/ignite/version.Date={{.Date}} -X github.com/ignite-hq/cli/ignite/version.Head={{.FullCommit}}
+      - -s -w -X github.com/ignite/cli/ignite/version.Version={{.Tag}} -X github.com/ignite/cli/ignite/version.Date={{.Date}} -X github.com/ignite/cli/ignite/version.Head={{.FullCommit}}
     goos:
       - linux
       - darwin

diff --git a/Makefile b/Makefile
@@ -5,8 +5,8 @@ PROJECT_NAME = ignite
 DATE := $(shell date '+%Y-%m-%dT%H:%M:%S')
 FIND_ARGS := -name '*.go' -type f -not -name '*.pb.go'
 HEAD = $(shell git rev-parse HEAD)
-LD_FLAGS = -X github.com/ignite-hq/cli/ignite/version.Head='$(HEAD)' \
-	-X github.com/ignite-hq/cli/ignite/version.Date='$(DATE)'
+LD_FLAGS = -X github.com/ignite/cli/ignite/version.Head='$(HEAD)' \
+	-X github.com/ignite/cli/ignite/version.Date='$(DATE)'
 BUILD_FLAGS = -mod=readonly -ldflags='$(LD_FLAGS)'
 BUILD_FOLDER = ./dist
 
@@ -37,7 +37,7 @@ govet:
 format:
 	@echo Formatting...
 	@find . $(FIND_ARGS) | xargs gofmt -d -s
-	@find . $(FIND_ARGS) | xargs goimports -w -local github.com/ignite-hq/cli
+	@find . $(FIND_ARGS) | xargs goimports -w -local github.com/ignite/cli
 
 ## lint: Run Golang CI Lint.
 lint:

diff --git a/actions/cli/readme.md b/actions/cli/readme.md
@@ -16,7 +16,7 @@ jobs:
         uses: actions/checkout@v2
 
       - name: Print Help 
-        uses: ignite-hq/cli/actions/cli@develop
+        uses: ignite/cli/actions/cli@develop
         with:
           args: -h 
 ```
diff --git a/changelog.md b/changelog.md
@@ -1,12 +1,12 @@
 # Changelog
 
-## [`v0.22.1`](https://github.com/ignite-hq/cli/releases/tag/v0.22.1)
+## [`v0.22.1`](https://github.com/ignite/cli/releases/tag/v0.22.1)
 
 ### Fixes 
 
 - Fix IBC module scaffolding interface in templates
 
-## [`v0.22.0`](https://github.com/ignite-hq/cli/releases/tag/v0.22.0)
+## [`v0.22.0`](https://github.com/ignite/cli/releases/tag/v0.22.0)
 
 ### Features 
 
@@ -17,13 +17,13 @@
 
 - Add a fix in code generation to avoid user's NodeJS configs to break TS client generation routine
 
-## [`v0.21.2`](https://github.com/ignite-hq/cli/releases/tag/v0.21.2)
+## [`v0.21.2`](https://github.com/ignite/cli/releases/tag/v0.21.2)
 
 ### Fixes 
 
 - Set min. gas to zero when running `chain` command set 
 
-## [`v0.21.1`](https://github.com/ignite-hq/cli/releases/tag/v0.21.1)
+## [`v0.21.1`](https://github.com/ignite/cli/releases/tag/v0.21.1)
 
 ### Features 
 
@@ -35,38 +35,38 @@
 - Fixed shell completion generation
 - Make sure proto package names are valid when using simple app names
 
-## [`v0.21.0`](https://github.com/ignite-hq/cli/releases/tag/v0.21.0)
+## [`v0.21.0`](https://github.com/ignite/cli/releases/tag/v0.21.0)
 
 ### Features 
 
 - Support simple app names when scaffolding chains. e.g.: `ignite scaffold chain mars`
 - Ask confirmation when scaffolding over changes that are not committed yet 
 
-## [`v0.20.4`](https://github.com/ignite-hq/cli/releases/tag/v0.20.4)
+## [`v0.20.4`](https://github.com/ignite/cli/releases/tag/v0.20.4)
 
 ### Fixes
 
 - Use `protoc` binary compiled in an older version of macOS AMD64 for backwards compatibility in code generation
 
-## [`v0.20.3`](https://github.com/ignite-hq/cli/releases/tag/v0.20.3)
+## [`v0.20.3`](https://github.com/ignite/cli/releases/tag/v0.20.3)
 
 ### Fixes
 
 - Use latest version of CLI in templates to fix Linux ARM support _(It's now possible to develop chains in Linux ARM machines and since the chain depends on the CLI in its go.mod, it needs to use the latest version that support ARM targets)_
 
-## [`v0.20.2`](https://github.com/ignite-hq/cli/releases/tag/v0.20.2)
+## [`v0.20.2`](https://github.com/ignite/cli/releases/tag/v0.20.2)
 
 ### Fixes
 
 - Use `unsafe-reset-all` cmd under `tendermint` cmd for chains that use `=> v0.45.3` version of Cosmos SDK
 
-## [`v0.20.1`](https://github.com/ignite-hq/cli/releases/tag/v0.20.1)
+## [`v0.20.1`](https://github.com/ignite/cli/releases/tag/v0.20.1)
 
 ### Features
 
 - Release the CLI with Linux ARM and native M1 binaries
 
-## [`v0.20.0`](https://github.com/ignite-hq/cli/releases/tag/v0.20.0)
+## [`v0.20.0`](https://github.com/ignite/cli/releases/tag/v0.20.0)
 
 Our new name is **Ignite CLI**!
 
@@ -78,7 +78,7 @@ Our new name is **Ignite CLI**!
 - Added support for in memory backend in `pkg/cosmosclient` package
 - Improved our tutorials and documentation
 
-## [`v0.19.5`](https://github.com/ignite-hq/cli/pull/2158/commits)
+## [`v0.19.5`](https://github.com/ignite/cli/pull/2158/commits)
 
 ### Features
 
@@ -104,7 +104,7 @@ Our new name is **Ignite CLI**!
 
 - Upgraded Flutter template to `v2.0.3`
 
-## [`v0.19.2`](https://github.com/ignite-hq/cli/milestone/14)
+## [`v0.19.2`](https://github.com/ignite/cli/milestone/14)
 
 ### Fixes
 
@@ -118,7 +118,7 @@ Our new name is **Ignite CLI**!
 
 ### Breaking Changes
 
-- Deprecated the Starport Modules [tendermint/spm](https://github.com/tendermint/spm) repo and moved the contents to the Ignite CLI repo [`ignite/pkg/`](https://github.com/ignite-hq/cli/tree/develop/ignite/pkg/) in [PR 1971](https://github.com/ignite-hq/cli/pull/1971/files) 
+- Deprecated the Starport Modules [tendermint/spm](https://github.com/tendermint/spm) repo and moved the contents to the Ignite CLI repo [`ignite/pkg/`](https://github.com/ignite/cli/tree/develop/ignite/pkg/) in [PR 1971](https://github.com/ignite/cli/pull/1971/files) 
 
     Updates are required if your chain uses these packages: 
 
@@ -127,7 +127,7 @@ Our new name is **Ignite CLI**!
     - `spm/openapiconsole` is now `pkg/openapiconsole`
     - `testutil/sample` is now `cosmostestutil/sample`
 
-- Updated the faucet HTTP API schema. See API changes in [fix: improve faucet reliability #1974](https://github.com/ignite-hq/cli/pull/1974/files#diff-0e157f4f60d6fbd95e695764df176c8978d85f1df61475fbfa30edef62fe35cd)
+- Updated the faucet HTTP API schema. See API changes in [fix: improve faucet reliability #1974](https://github.com/ignite/cli/pull/1974/files#diff-0e157f4f60d6fbd95e695764df176c8978d85f1df61475fbfa30edef62fe35cd)
 
 ## `v0.19.1`
 

diff --git a/contributing.md b/contributing.md
@@ -12,7 +12,7 @@
 
 Before you create a new PR on Ignite CLI, make sure that you read and comply with this document.
 
-Start a new [Discussion](https://github.com/ignite-hq/cli/discussions/new) if you want to propose changes to this document.
+Start a new [Discussion](https://github.com/ignite/cli/discussions/new) if you want to propose changes to this document.
 
 To prepare for success, see [Set Up Your Ignite CLI Development Environment](dev-env-setup.md).
 
@@ -22,9 +22,9 @@ Thank you for your contribution!
 
 ## Providing Feedback
 
-- Before you open an issue, do a web search, and check for [existing open and closed GitHub Issues](https://github.com/ignite-hq/cli/issues) to see if your question has already been asked and answered. If you find a relevant topic, you can comment on that issue.
+- Before you open an issue, do a web search, and check for [existing open and closed GitHub Issues](https://github.com/ignite/cli/issues) to see if your question has already been asked and answered. If you find a relevant topic, you can comment on that issue.
 
-- To provide feedback or ask a question, create a [GitHub issue](https://github.com/ignite-hq/cli/issues/new/choose). Be sure to provide the relevant information, case study, or informative links as suggested by the Pull Request template.
+- To provide feedback or ask a question, create a [GitHub issue](https://github.com/ignite/cli/issues/new/choose). Be sure to provide the relevant information, case study, or informative links as suggested by the Pull Request template.
 
 - We recommend using GitHub issues for issues and feedback. However, you can ask quick questions on the **#🛠️ build-chains** channel in the official [Ignite Discord](https://discord.gg/ignite).
 
@@ -70,7 +70,7 @@ If you started a PR but couldn't finish it for whatever reason, don't give up. I
 
 Ignite CLI follows Git Flow for branch strategy <https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow>.
 
-- Each Ignite CLI release has a milestone, see <https://github.com/ignite-hq/cli/milestones>.
+- Each Ignite CLI release has a milestone, see <https://github.com/ignite/cli/milestones>.
 
 - Issues in each milestone have a **priority/high**, **priority/medium**, or **priority/low** label.
 
@@ -82,8 +82,8 @@ Ignite CLI follows Git Flow for branch strategy <https://www.atlassian.com/git/t
 
   - Issues in the **Next** milestone usually have a lower priority than milestones that are associated with a release version, like **Milestone v0.1.0**.
 
-- A single project board <https://github.com/ignite-hq/cli/projects/4> shows the issues we are currently working on and what issues we plan to work on.
+- A single project board <https://github.com/ignite/cli/projects/4> shows the issues we are currently working on and what issues we plan to work on.
 
-Contributors, check the **To Do** column on the project board <https://github.com/ignite-hq/cli/projects/4> to find an issue to work on. See the [Ignite CLI bounty program](docs/bounty/index.md) to learn how your participation can earn rewards.
+Contributors, check the **To Do** column on the project board <https://github.com/ignite/cli/projects/4> to find an issue to work on. See the [Ignite CLI bounty program](docs/bounty/index.md) to learn how your participation can earn rewards.
 
 We appreciate your contribution!
diff --git a/dev-env-setup.md b/dev-env-setup.md
@@ -43,7 +43,7 @@ See [Install Ignite CLI](docs/install.md).
 
 ## Clone the Ignite CLI repo
 
-`git clone --depth=1 [email protected]:ignite-hq/cli.git`
+`git clone --depth=1 [email protected]:ignite/cli.git`
 
 ## Run make install
 

diff --git a/docs/docs/06-bounty.md b/docs/docs/06-bounty.md
@@ -7,7 +7,7 @@ description: Ignite CLI bounty program incentives and rewards.
 
 Our Ignite CLI bounty program provides incentives for your participation and pays rewards. If you know Golang, follow the bounty issues, write code, close issues, and get rewarded.
 
-Do your bounty hunting in our repo. Track new, in-progress, and completed bounties on the [Bounty board](https://github.com/ignite-hq/cli/projects/5) in GitHub.
+Do your bounty hunting in our repo. Track new, in-progress, and completed bounties on the [Bounty board](https://github.com/ignite/cli/projects/5) in GitHub.
 
 For details on the Ignite CLI bounty program, join the #bounty channel in [Ignite Discord](https://discord.com/invite/ignite). 
 

diff --git a/docs/docs/contributing/01-contributing.md b/docs/docs/contributing/01-contributing.md
@@ -11,7 +11,7 @@ To set up your environment for success, follow the [technical setup](02-technica
 
 ## Using this repo
 
-Review existing [Ignite CLI issues](https://github.com/ignite-hq/cli/issues) to see if your question has already been asked and answered.
+Review existing [Ignite CLI issues](https://github.com/ignite/cli/issues) to see if your question has already been asked and answered.
 
 - To provide feedback, file an issue and provide generous details to help us understand how we can make it better.
 - To provide a fix, make a direct contribution. If you're not a member or maintainer, fork the repo and then submit a pull request (PR) from your forked repo to the `develop` branch.
@@ -63,7 +63,7 @@ As always, work-in-progress content might be happening in other locations and re
 
 The Ignite product team developers are focused on building Ignite CLI and improving the developer experience. The Ignite Ecosystem Development team owns the technical content and tutorials and manages developer onboarding.
 
-Meet the [people behind Ignite CLI and our contributors](https://github.com/ignite-hq/cli/graphs/contributors).
+Meet the [people behind Ignite CLI and our contributors](https://github.com/ignite/cli/graphs/contributors).
 
 ## Viewing docs builds
 

diff --git a/docs/docs/contributing/02-technical-setup.md b/docs/docs/contributing/02-technical-setup.md
@@ -25,7 +25,7 @@ Click the GitHub icon in the sidebar for GitHub integration and follow the promp
 
 ## Clone the repos that you work in
 
-- Fork or clone the <https://github.com/ignite-hq/cli/> repository.
+- Fork or clone the <https://github.com/ignite/cli/> repository.
 
 Internal Ignite users have different permissions. If you're not sure, fork the repo.
 

diff --git a/docs/docs/contributing/templates/01-concept_template.md b/docs/docs/contributing/templates/01-concept_template.md
@@ -12,7 +12,7 @@ We admire and respect these resources:
 - Google developer documentation [style guide](https://developers.google.com/style)
 - Digital Ocean style guide [do.co/style](https://do.co/style)
 
-[Create an issue](https://github.com/ignite-hq/cli/issues/new/choose) to let us know if you have questions. 
+[Create an issue](https://github.com/ignite/cli/issues/new/choose) to let us know if you have questions. 
 
 -->
 

diff --git a/docs/docs/contributing/templates/02-tutorial-template.md b/docs/docs/contributing/templates/02-tutorial-template.md
@@ -12,7 +12,7 @@ We admire, respect, and rely on these resources:
 - Google developer documentation [style guide](https://developers.google.com/style)
 - Digital Ocean style guide [do.co/style](https://do.co/style)
 
-[Create an issue](https://github.com/ignite-hq/cli/issues/new/choose) to let us know if you have questions. 
+[Create an issue](https://github.com/ignite/cli/issues/new/choose) to let us know if you have questions. 
 
 -->
 

diff --git a/docs/docs/guide/01-install.md b/docs/docs/guide/01-install.md
@@ -5,7 +5,7 @@ description: Steps to install Ignite CLI on your local computer.
 
 # Install Ignite CLI 
 
-You can run [Ignite CLI](https://github.com/ignite-hq/cli) in a web-based Gitpod IDE or you can install Ignite CLI on your local computer.
+You can run [Ignite CLI](https://github.com/ignite/cli) in a web-based Gitpod IDE or you can install Ignite CLI on your local computer.
 
 ## Prerequisites
 
@@ -44,7 +44,7 @@ curl https://get.ignite.com/cli! | bash
 
 This command invokes `curl` to download the install script and pipes the output to `bash` to perform the installation. The `ignite` binary is installed in `/usr/local/bin`.
 
-To learn more or customize the installation process, see the [installer docs](https://github.com/ignite-hq/installer) on GitHub.
+To learn more or customize the installation process, see the [installer docs](https://github.com/ignite/installer) on GitHub.
 
 ### Write permission
 
@@ -87,14 +87,14 @@ To remove the current Ignite CLI installation:
 
 After all existing Ignite CLI installations are removed, follow the  [Installing Ignite CLI](#installing-ignite-cli) instructions.
 
-For details on version features and changes, see the [changelog.md](https://github.com/ignite-hq/cli/blob/develop/changelog.md) in the repo.
+For details on version features and changes, see the [changelog.md](https://github.com/ignite/cli/blob/develop/changelog.md) in the repo.
 
 ## Build from source
 
 To experiment with the source code, you can build from source:
 
 ```bash
-git clone https://github.com/ignite-hq/cli --depth=1
+git clone https://github.com/ignite/cli --depth=1
 cd cli && make install
 ```
 

diff --git a/docs/docs/guide/02-hello.md b/docs/docs/guide/02-hello.md
@@ -9,7 +9,7 @@ This tutorial is a great place to start your journey into the Cosmos ecosystem.
 
 ## Get started
 
-In the previous chapter you've learned how to install [Ignite CLI](https://github.com/ignite-hq/cli), the tool that offers everything you need to build, test, and launch your blockchain with a decentralized worldwide community.
+In the previous chapter you've learned how to install [Ignite CLI](https://github.com/ignite/cli), the tool that offers everything you need to build, test, and launch your blockchain with a decentralized worldwide community.
 
 This series of tutorials is based on a specific version of Ignite CLI, so be sure to install the correct version. For example, to install Ignite CLI v0.20.0 use the following command:
 

diff --git a/docs/docs/guide/03-blog/02-connect-blockchain.md b/docs/docs/guide/03-blog/02-connect-blockchain.md
@@ -48,7 +48,7 @@ go 1.17
 
 require (
 	github.com/username/blog v0.0.0-00010101000000-000000000000
-	github.com/ignite-hq/cli v0.19.2 
+	github.com/ignite/cli v0.22.2
 )
 
 replace github.com/username/blog => ../blog
@@ -79,7 +79,7 @@ import (
 	// importing the types package of your blog blockchain
 	"github.com/username/blog/x/blog/types"
 	// importing the general purpose Cosmos blockchain client
-	"github.com/ignite-hq/cli/ignite/pkg/cosmosclient"
+	"github.com/ignite/cli/ignite/pkg/cosmosclient"
 )
 
 func main() {
@@ -136,7 +136,7 @@ func main() {
 Read the comments in the code carefully to learn details about each line of code.
 
 To learn more about the `cosmosclient` package, see the Go 
-[cosmosclient](https://pkg.go.dev/github.com/ignite-hq/cli/ignite/pkg/cosmosclient) package documentation. Details are provided to learn how to use the `Client` type with `Options` and `KeyringBackend`.
+[cosmosclient](https://pkg.go.dev/github.com/ignite/cli/ignite/pkg/cosmosclient) package documentation. Details are provided to learn how to use the `Client` type with `Options` and `KeyringBackend`.
 
 ## Run the blockchain and the client