-
Notifications
You must be signed in to change notification settings - Fork 102
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
Noble Network Support #833
Conversation
Thank you so much! Namespace is correct, it's just the binary name capitalised. I'll include in the next release |
Co-authored-by: Tom Beynon <[email protected]>
Pre-release image: |
@PoolPirate any chance you can allow me to edit this PR so I can fix the conflicts? Sorry I should have merged this one first. |
@tombeynon Don't have the option to enable that in the PR for some reason. Did resolve conflicts myself for this one, will see where I can enable that going forward |
Ah well I see you mean to merge this for the next release. |
I've come across that before, I don't think it's possible for organisation forks which is very annoying.. appreciate the invite though, that'll work great in the future. I'll do another release with just this PR shortly, the release process has to be completed quickly once started as it breaks e.g. Akash Console. I wasn't sure you'd respond this quick 😅 |
Github broke so I had to cancel the action anyway |
Adding support for the noble blockchain.
Don't know how to validate that
NAMESPACE
is correct, been using this for a while now and its been working just fine tho.