-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Move polkadot build check to polkadot and check status in substrate #6706
Conversation
Forked at: 60e3a69 Parent branch: origin/master
Co-authored-by: Benjamin Kampmann <ben@gnunicorn.org>
This reverts commit c133c59.
This reverts commit 502aba4.
This reverts commit 4e15214.
This reverts commit ee5e13c.
This reverts commit 1b91a8c.
Parent branch: origin/master Forked at: 4da2926
Parent branch: origin/master Forked at: 4da2926
Parent branch: origin/master Forked at: 4da2926
Parent branch: origin/master Forked at: 4da2926
a66a759
to
5f07368
Compare
Parent branch: origin/master Forked at: 4da2926
Parent branch: origin/master Forked at: 4da2926
@TriplEight as you can see now the polkadot-companion-status step fails because the polkadot companion PR has not been approved yet. (I still need to finish some things in polkadot .gitlab-ci.yml) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI and bash parts look good!
@TriplEight It is almost ready to merge but I won't be able to do it alone:
(The reason for 3. is because on substrate it checks the status of the polkadot PR while on Polkadot it needs to know which branch of substrate needs to be used for the build) |
We should probably also remove or edit
We'll need to get someone in the dev-admin team to do this. |
(Wait before doing so because there is still this problem of Cargo.lock to update in polkadot) |
I'm closing this PR because after discussion (and checking history) I realized that this solution won't solve the issue I currently have with the companion pr process. |
More details in paritytech/polkadot#1426
polkadot companion: paritytech/polkadot#1426