Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove IBC Anywhere and add Skip:Go #169

Merged
merged 2 commits into from
Nov 5, 2024
Merged

Conversation

gjermundgaraba
Copy link
Contributor

Talked with @Reecepbcups and was told that IBC Anywhere is not going to be hosted anymore.

Also adding Skip:Go which is useful to have here, I believe.

IBC Anywhere is not going to be hosted anymore
README.md Outdated
@@ -251,7 +251,7 @@ Templates to help you get started with building a Cosmos SDK blockchain.
* [REStake](https://restake.app) - Auto-compounder app for Cosmos blockchains using Authz ([source](https://github.com/eco-stake/restake)).
* [Cosmfaucet](https://github.com/scalalang2/cosmfaucet) - Self-hosted faucet service for Cosmos based blockchain.
* [Cosmos Notifier](https://cosmos-notifier.decrypto.online) - Governance notification tool for Telegram and Discord ([source](https://github.com/shifty11/cosmos-notifier)).
* [IBC Anywhere](https://ibc.reece.sh/) - IBC token transfers including multi-chain hops.
* [Skip:Go](https://go.skip.build) - IBC token transfers, automated swapping and multi-hop routing
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it open source?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@julienrbrt julienrbrt Nov 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could it be added in here then, like the others.
Additionally could you fix the linter

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have updated with the source, and also removed the .markdownlint.json (because it does not seem to be needed (the linter we run in CI does not use this file)).

There is one thing I cannot fix for the linter (unless we disable that rule):

  README.md:1:1
  ✖  1:1  The repository should have "awesome" as a GitHub topic       remark-lint:awesome-github
  ✖  1:1  The repository should have "awesome-list" as a GitHub topic  remark-lint:awesome-github

  2 errors

But if you can add awesome and awesome-list as topics to the repo, the linter should pass now.

@julienrbrt julienrbrt merged commit 7f9412c into cosmos:main Nov 5, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants