Please consider not doing this. The ref for any stack repo can be passed on the stack orchestrator command line like: `--branches <repo>@<ref>`, see: https://git.vdb.to/cerc-io/stack-orchestrator/src/branch/main/stack_orchestrator/repos/setup_repositories.py#L187
This allows the stack to define only the repositories and removes the need for the stack file to be constantly maintained (or conversely ossify referring to a stale version).
This pull request has changes conflicting with the target branch.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of laconicd testnet validator enrollment
@@ -3,3 +3,3 @@description: "A laconicd fixturenet"repos:- git.vdb.to/cerc-io/laconicd- git.vdb.to/cerc-io/laconicd@v0.1.5Please consider not doing this. The ref for any stack repo can be passed on the stack orchestrator command line like:
--branches <repo>@<ref>, see: https://git.vdb.to/cerc-io/stack-orchestrator/src/branch/main/stack_orchestrator/repos/setup_repositories.py#L187This allows the stack to define only the repositories and removes the need for the stack file to be constantly maintained (or conversely ossify referring to a stale version).
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.