You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
polkadot/cumulus/substrate will be merged to one repository (something like polkadot-sdk)
How will it impact command-bot?
Since the runtimes are moved out to fellowship org, as stated in forum post, the only thing to test try-runtime and benchmark remains substrate dev pallet. So command-bot-scripts for substrate have to be updated to run it from polkadot-sdk considering the subfolder "substrate" from root of repo + the paths for weights
To simplify usage of command-bot scripts in monorepo, it's better to support "default arguments" which is only possible with named arguments (vs positioned that we have now). This leads also to a change of how we run the commands
Share credits for idea & part of implementation with @mutantcornholio
- Fixes#160
- Related #174
- Implements named arguments for #174 + handy "guess" helper which translates old to a new syntax
- Improved docs which now filterable by repo and have better command arguments description
- Made "bot ..." configurable in env vars, so we can run local bots on **paritytech-stg** in same repo alongside with staging bots and not interfere
Prepare command-bot scripts to work in monorepo & runtimes in fellowship
Context:
What's going to change
How will it impact command-bot?
Since the runtimes are moved out to fellowship org, as stated in forum post, the only thing to test try-runtime and benchmark remains substrate
dev
pallet. So command-bot-scripts for substrate have to be updated to run it from polkadot-sdk considering the subfolder "substrate" from root of repo + the paths for weightsTo simplify usage of command-bot scripts in monorepo, it's better to support "default arguments" which is only possible with named arguments (vs positioned that we have now). This leads also to a change of how we run the commands
Tasks
The text was updated successfully, but these errors were encountered: