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
We constantly need to test our updates. The problem is that updates in submodules may depend on each other - and we need to test it before merging the updates.
Currently, we need to do it manually, which gives us a lot of pain.
A perfect user story looks like that:
Developer starts developing from an issue in zkllvm repository
(Assuming that this issue requires changes in both assigner and circifier) - developer makes changes in feature-branches and creates PRs in all repos (except from zkllvm repository - because zkllvm PR requires merging PRs in submodules first)
Dependent PRs are being detected by a bot. It runs dependent testing on corresponding branches.
If all good - Bot approves all PRs
Another developer approves these PRs.
PRs in submodules rebase to master
Bot creates PR in zkllvm (I am not sure if we need this step).
Maybe this can be done by giving branches the same names. It is not very convenient, and it also depends on human factor.
Another option - keywords or labels in PRs. This would require a minimum job done by the developer to trigger correct bot behavior.
The text was updated successfully, but these errors were encountered:
We constantly need to test our updates. The problem is that updates in submodules may depend on each other - and we need to test it before merging the updates.
Currently, we need to do it manually, which gives us a lot of pain.
A perfect user story looks like that:
assigner
andcircifier
) - developer makes changes in feature-branches and creates PRs in all repos (except from zkllvm repository - because zkllvm PR requires merging PRs in submodules first)Maybe this can be done by giving branches the same names. It is not very convenient, and it also depends on human factor.
Another option - keywords or labels in PRs. This would require a minimum job done by the developer to trigger correct bot behavior.
The text was updated successfully, but these errors were encountered: