We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the sovereign-sdk-wip demo-rollup READMEs emit this output:
sovereign-sdk-wip
Unknown bashtestmd tag, ignoring: shell Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: sh Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: sh Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: sh Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: sh Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: sh Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: bash Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: bash Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: bash Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: bash Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: bash Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: sh Unknown bashtestmd tag, ignoring: test-ci Unknown bashtestmd tag, ignoring: bash Unknown bashtestmd tag, ignoring: test-ci
It's not immediately clear whether one should worry about this. The solution is to not warnings for:
bash
shell
sh
only_tag
The text was updated successfully, but these errors were encountered:
Fixed by #3.
Sorry, something went wrong.
No branches or pull requests
Currently, the
sovereign-sdk-wip
demo-rollup READMEs emit this output:It's not immediately clear whether one should worry about this. The solution is to not warnings for:
bash
shell
/sh
only_tag
The text was updated successfully, but these errors were encountered: