From 555668a8248c35296c723462a24b42ff13659ec9 Mon Sep 17 00:00:00 2001 From: Danilo Pantani Date: Thu, 20 Mar 2025 00:52:28 -0300 Subject: [PATCH 1/4] fix some broken links --- docs/docs/04-clients/02-typescript.md | 2 +- docs/docs/04-network/01-chain.md | 2 +- docs/docs/08-references/01-cli.md | 2 +- docs/versioned_docs/version-v0.25/clients/01-typescript.md | 2 +- docs/versioned_docs/version-v0.26/03-clients/02-typescript.md | 2 +- docs/versioned_docs/version-v0.26/04-network/01-chain.md | 2 +- docs/versioned_docs/version-v0.27/03-clients/02-typescript.md | 2 +- docs/versioned_docs/version-v0.27/04-network/01-chain.md | 2 +- docs/versioned_docs/version-v28/03-clients/02-typescript.md | 2 +- docs/versioned_docs/version-v28/04-network/01-chain.md | 2 +- ignite/cmd/scaffold_chain_registry.go | 2 +- 11 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/docs/04-clients/02-typescript.md b/docs/docs/04-clients/02-typescript.md index 5cfbf7705d..5d83388d8e 100644 --- a/docs/docs/04-clients/02-typescript.md +++ b/docs/docs/04-clients/02-typescript.md @@ -353,7 +353,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner` interface, so you can simply replace the `wallet` argument in client instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr requires information about your chain, like chain ID, denoms, fees, etc. -[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is +[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is a method Keplr provides to pass this information to the Keplr extension. The generated client makes this easier by offering a `useKeplr()` method that diff --git a/docs/docs/04-network/01-chain.md b/docs/docs/04-network/01-chain.md index 4edf0a91cb..45a665887a 100644 --- a/docs/docs/04-network/01-chain.md +++ b/docs/docs/04-network/01-chain.md @@ -9,7 +9,7 @@ description: Ignite Chain. _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._ -Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. +Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set. diff --git a/docs/docs/08-references/01-cli.md b/docs/docs/08-references/01-cli.md index 44a102335d..8d35b88cfa 100644 --- a/docs/docs/08-references/01-cli.md +++ b/docs/docs/08-references/01-cli.md @@ -2696,7 +2696,7 @@ Configs for the chain registry Scaffold the chain registry chain.json and assets.json files. -The chain registry is a GitHub repo, hosted at https://github.com/cosmos/cosmos-registry, that +The chain registry is a GitHub repo, hosted at https://github.com/cosmos/chain-registry, that contains the chain.json and assets.json files of most of chains in the Cosmos ecosystem. It is good practices, when creating a new chain, and about to launch a testnet or mainnet, to publish the chain's metadata in the chain registry. diff --git a/docs/versioned_docs/version-v0.25/clients/01-typescript.md b/docs/versioned_docs/version-v0.25/clients/01-typescript.md index 4dd8e148e3..a6fb8b0f58 100644 --- a/docs/versioned_docs/version-v0.25/clients/01-typescript.md +++ b/docs/versioned_docs/version-v0.25/clients/01-typescript.md @@ -249,7 +249,7 @@ const client = new Client({ ); ``` -The problem is that for a new Ignite CLI scaffolded chain, Keplr has no knowledge of it thus requiring an initial call to [`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) method to add the chain information to the user's Keplr instance. +The problem is that for a new Ignite CLI scaffolded chain, Keplr has no knowledge of it thus requiring an initial call to [`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) method to add the chain information to the user's Keplr instance. The generated client makes this easier by offering a `useKeplr()` method that autodiscovers the chain information and sets it up for you. Thus you can instantiate the client without a wallet and then call `useKeplr()` to enable transacting via Keplr like so: diff --git a/docs/versioned_docs/version-v0.26/03-clients/02-typescript.md b/docs/versioned_docs/version-v0.26/03-clients/02-typescript.md index 5cfbf7705d..5d83388d8e 100644 --- a/docs/versioned_docs/version-v0.26/03-clients/02-typescript.md +++ b/docs/versioned_docs/version-v0.26/03-clients/02-typescript.md @@ -353,7 +353,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner` interface, so you can simply replace the `wallet` argument in client instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr requires information about your chain, like chain ID, denoms, fees, etc. -[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is +[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is a method Keplr provides to pass this information to the Keplr extension. The generated client makes this easier by offering a `useKeplr()` method that diff --git a/docs/versioned_docs/version-v0.26/04-network/01-chain.md b/docs/versioned_docs/version-v0.26/04-network/01-chain.md index 4edf0a91cb..45a665887a 100644 --- a/docs/versioned_docs/version-v0.26/04-network/01-chain.md +++ b/docs/versioned_docs/version-v0.26/04-network/01-chain.md @@ -9,7 +9,7 @@ description: Ignite Chain. _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._ -Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. +Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set. diff --git a/docs/versioned_docs/version-v0.27/03-clients/02-typescript.md b/docs/versioned_docs/version-v0.27/03-clients/02-typescript.md index c770f5c338..2836cc81d9 100644 --- a/docs/versioned_docs/version-v0.27/03-clients/02-typescript.md +++ b/docs/versioned_docs/version-v0.27/03-clients/02-typescript.md @@ -354,7 +354,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner` interface, so you can simply replace the `wallet` argument in client instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr requires information about your chain, like chain ID, denoms, fees, etc. -[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is +[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is a method Keplr provides to pass this information to the Keplr extension. The generated client makes this easier by offering a `useKeplr()` method that diff --git a/docs/versioned_docs/version-v0.27/04-network/01-chain.md b/docs/versioned_docs/version-v0.27/04-network/01-chain.md index 4edf0a91cb..45a665887a 100644 --- a/docs/versioned_docs/version-v0.27/04-network/01-chain.md +++ b/docs/versioned_docs/version-v0.27/04-network/01-chain.md @@ -9,7 +9,7 @@ description: Ignite Chain. _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._ -Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. +Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set. diff --git a/docs/versioned_docs/version-v28/03-clients/02-typescript.md b/docs/versioned_docs/version-v28/03-clients/02-typescript.md index 5cfbf7705d..5d83388d8e 100644 --- a/docs/versioned_docs/version-v28/03-clients/02-typescript.md +++ b/docs/versioned_docs/version-v28/03-clients/02-typescript.md @@ -353,7 +353,7 @@ Normally, Keplr provides a wallet object implementing the `OfflineSigner` interface, so you can simply replace the `wallet` argument in client instantiation with `window.keplr.getOfflineSigner(chainId)`. However, Keplr requires information about your chain, like chain ID, denoms, fees, etc. -[`experimentalSuggestChain()`](https://docs.keplr.app/api/suggest-chain.html) is +[`experimentalSuggestChain()`](https://docs.keplr.app/api/guide/suggest-chain) is a method Keplr provides to pass this information to the Keplr extension. The generated client makes this easier by offering a `useKeplr()` method that diff --git a/docs/versioned_docs/version-v28/04-network/01-chain.md b/docs/versioned_docs/version-v28/04-network/01-chain.md index 4edf0a91cb..45a665887a 100644 --- a/docs/versioned_docs/version-v28/04-network/01-chain.md +++ b/docs/versioned_docs/version-v28/04-network/01-chain.md @@ -9,7 +9,7 @@ description: Ignite Chain. _Ignite is a blockchain to help launch Cosmos SDK-based blockchains._ -Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://v1.cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. +Using Cosmos SDK and Ignite CLI, developers can quickly create a crypto application that is decentralized, economical for usage, and scalable. The Cosmos SDK framework allows developers to create sovereign application-specific blockchains that become part of the wider [Cosmos ecosystem](https://cosmos.network/ecosystem/apps). Blockchains created with Cosmos SDK use a Proof-of-Stake (PoS) consensus protocol that requires validators to secure the chain. Even though tools like Ignite CLI simplify the development of a Cosmos SDK blockchain, launching a new chain is a highly complex process. One of the major challenges of developing and launching your own sovereign blockchain is ensuring the security of the underlying consensus. Since Cosmos SDK chains are based on the PoS consensus, each blockchain requires initial coin allocations and validators before they can be launched, which presents developers with significant challenges, such as determining their chain's tokenomics or coordinating a robust validator set. diff --git a/ignite/cmd/scaffold_chain_registry.go b/ignite/cmd/scaffold_chain_registry.go index 914a9ad691..6a106d48d6 100644 --- a/ignite/cmd/scaffold_chain_registry.go +++ b/ignite/cmd/scaffold_chain_registry.go @@ -15,7 +15,7 @@ func NewScaffoldChainRegistry() *cobra.Command { Short: "Configs for the chain registry", Long: `Scaffold the chain registry chain.json and assets.json files. -The chain registry is a GitHub repo, hosted at https://github.com/cosmos/cosmos-registry, that +The chain registry is a GitHub repo, hosted at https://github.com/cosmos/chain-registry, that contains the chain.json and assets.json files of most of chains in the Cosmos ecosystem. It is good practices, when creating a new chain, and about to launch a testnet or mainnet, to publish the chain's metadata in the chain registry. From ed43cfa468de300033d5858ebb0cf7b4140715b5 Mon Sep 17 00:00:00 2001 From: Danilo Pantani Date: Thu, 20 Mar 2025 00:58:27 -0300 Subject: [PATCH 2/4] fix social links --- .github/workflows/md-link-checker-config.json | 3 --- .github/workflows/md-link-checker.yml | 2 +- docs/docusaurus.config.js | 4 ++-- .../versioned_docs/version-v0.25/guide/05-scavenge/01-hunt.md | 2 +- readme.md | 2 +- 5 files changed, 5 insertions(+), 8 deletions(-) diff --git a/.github/workflows/md-link-checker-config.json b/.github/workflows/md-link-checker-config.json index e70d47c119..bd909330b0 100644 --- a/.github/workflows/md-link-checker-config.json +++ b/.github/workflows/md-link-checker-config.json @@ -1,8 +1,5 @@ { "ignorePatterns": [ - { - "pattern": "^https://twitter.com" - }, { "pattern": "^https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request" }, diff --git a/.github/workflows/md-link-checker.yml b/.github/workflows/md-link-checker.yml index cad9f2624b..22cf27a90a 100644 --- a/.github/workflows/md-link-checker.yml +++ b/.github/workflows/md-link-checker.yml @@ -15,7 +15,7 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - - uses: gaurav-nelson/github-action-markdown-link-check@1.0.13 + - uses: gaurav-nelson/github-action-markdown-link-check@1.0.16 with: folder-path: "." use-verbose-mode: "yes" diff --git a/docs/docusaurus.config.js b/docs/docusaurus.config.js index 1775c3e1f0..2d78aa89ab 100644 --- a/docs/docusaurus.config.js +++ b/docs/docusaurus.config.js @@ -205,11 +205,11 @@ const config = { }, { label: "Twitter", - href: "https://twitter.com/ignite_com", + href: "https://x.com/ignite", }, { label: "Linkedin", - href: "https://www.linkedin.com/company/ignt/", + href: "https://www.linkedin.com/company/allinbits", }, { label: "YouTube", diff --git a/docs/versioned_docs/version-v0.25/guide/05-scavenge/01-hunt.md b/docs/versioned_docs/version-v0.25/guide/05-scavenge/01-hunt.md index 74e2f6eb54..dc590daa1e 100644 --- a/docs/versioned_docs/version-v0.25/guide/05-scavenge/01-hunt.md +++ b/docs/versioned_docs/version-v0.25/guide/05-scavenge/01-hunt.md @@ -11,7 +11,7 @@ In this tutorial, you will build a blockchain for a scavenger hunt game and lear * Implement custom logic in the CLI commands * Use an escrow account to store tokens -This tutorial was first presented as a workshop at GODays 2020 Berlin by [Billy Rennekamp](https://twitter.com/billyrennekamp). +This tutorial was first presented as a workshop at GODays 2020 Berlin by [Billy Rennekamp](https://x.com/billyrennekamp). This session aims to get you thinking about what is possible when developing applications that have access to **digital scarcity as a primitive**. The easiest way to think of scarcity is as money; If money grew on trees it would stop being _scarce_ and stop having value. diff --git a/readme.md b/readme.md index 940e3bb8d6..756a91776c 100644 --- a/readme.md +++ b/readme.md @@ -269,7 +269,7 @@ Ignite CLI is a free and open source product maintained by [Ignite](https://ignite.com). Here's where you can find us. Stay in touch. - [ignite.com website](https://ignite.com) -- [@ignite on Twitter](https://twitter.com/ignite) +- [@ignite on Twitter](https://x.com/ignite) - [ignite.com/blog](https://ignite.com/blog) - [Ignite Discord](https://discord.com/invite/ignite) - [Ignite YouTube](https://www.youtube.com/@ignitehq) From c0f2e79e7c96aa971a08f15b29bb7579086fdf63 Mon Sep 17 00:00:00 2001 From: Danilo Pantani Date: Thu, 20 Mar 2025 01:00:24 -0300 Subject: [PATCH 3/4] add changelog --- changelog.md | 1 + 1 file changed, 1 insertion(+) diff --git a/changelog.md b/changelog.md index dc29a27b3c..eba84c19b7 100644 --- a/changelog.md +++ b/changelog.md @@ -9,6 +9,7 @@ ### Changes - [#4569](https://github.com/ignite/cli/pull/4569) Add flags to set coin type on commands. Add getters for bech32 prefix and coin type. +- [#4589](https://github.com/ignite/cli/pull/4589) Fix broken links ### Fixes From abf49c3b06e94b9395afd05092abeabdaa3d156f Mon Sep 17 00:00:00 2001 From: Danilo Pantani Date: Thu, 20 Mar 2025 01:54:43 -0300 Subject: [PATCH 4/4] rename link action --- .../{md-link-checker-config.json => link-checker-config.json} | 0 .github/workflows/{md-link-checker.yml => link-checker.yml} | 4 ++-- 2 files changed, 2 insertions(+), 2 deletions(-) rename .github/workflows/{md-link-checker-config.json => link-checker-config.json} (100%) rename .github/workflows/{md-link-checker.yml => link-checker.yml} (81%) diff --git a/.github/workflows/md-link-checker-config.json b/.github/workflows/link-checker-config.json similarity index 100% rename from .github/workflows/md-link-checker-config.json rename to .github/workflows/link-checker-config.json diff --git a/.github/workflows/md-link-checker.yml b/.github/workflows/link-checker.yml similarity index 81% rename from .github/workflows/md-link-checker.yml rename to .github/workflows/link-checker.yml index 22cf27a90a..5cea7af619 100644 --- a/.github/workflows/md-link-checker.yml +++ b/.github/workflows/link-checker.yml @@ -1,4 +1,4 @@ -name: Check Markdown links +name: Check links on: pull_request: push: @@ -19,4 +19,4 @@ jobs: with: folder-path: "." use-verbose-mode: "yes" - config-file: ".github/workflows/md-link-checker-config.json" + config-file: ".github/workflows/link-checker-config.json"