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
Hi - can you create a branch named 130_reorg@main and replace the downstream dependency on teal.devel with teal.widgets please - i.e. replace:
insightsengineering/teal.devel: repo: insightsengineering/teal.devel host: https://github.com
with
insightsengineering/teal.widgets: repo: insightsengineering/teal.widgets host: https://github.com
And then when the rest of the merge is ready we can merge this PR in.
The right answer is (?) for NEST to have rtables as an external dependency not an internal one but in the mean time, there may be questions like this.
@gmbecker - can you do this and maybe add branch creation rights to some of the NEST developers?
The text was updated successfully, but these errors were encountered:
already done
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Hi - can you create a branch named 130_reorg@main and replace the downstream dependency on teal.devel with teal.widgets please - i.e. replace:
with
And then when the rest of the merge is ready we can merge this PR in.
The right answer is (?) for NEST to have rtables as an external dependency not an internal one but in the mean time, there may be questions like this.
@gmbecker - can you do this and maybe add branch creation rights to some of the NEST developers?
The text was updated successfully, but these errors were encountered: