-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
[EngAut] Polkadot Fellowship Automation - Q2 2024 #8
Comments
Currently blocked in polkadot-fellows/runtimes#192. Waiting for reply from the fellowship. We are checking if paritytech/review-bot#92 can be closed as the runtimes have separated the current situation. paritytech/up-to-date-action#14 is waiting for polkadot-fellows/runtimes#272 to be merged |
I finally managed to properly solve the problem in: Now I'm waiting for new reviews as I have drastically changed the code. I implemented the solutions from: |
Waiting for the following PRs to be reviewed/merged: |
Still waiting for this PRs to be reviewed. |
Merged the following PRs
Resolved the following tickets: |
A bug was reported for an individual case. No new updates. |
polkadot-fellows/xcm-format#65 was created as a requirement for polkadot-fellows/xcm-format#62 (comment) |
Added paritytech/review-bot#122 as a task |
Opened a PR for Weights generation polkadot-fellows/runtimes#406 |
Released and deployed review-bot and get-fellows-action, using People parachain. |
Updated all CI dependencies |
No updates this week, still waiting Basti & Tugy to spawn a runner. PR is ready |
This one was merged, so closing the epic |
Tasks
Fail when author pushes new code
should check if the user is not a fellow polkadot-fellows/runtimes#372The text was updated successfully, but these errors were encountered: