Skip to content
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

Port safe commits from master to polkadot-staging #2761

Merged
merged 3 commits into from
Jan 11, 2024

Conversation

svyatonik
Copy link
Contributor

opening early for visibility - could be reviewed commit-by-commit

Since we are now closer to moving to polkadot-sdk than to developing bridges-v2 + some parts of v2 have been already merged to the polkadot-staging, maybe we should start picking some commits from master and merge them to polkadot-staging. I'll start with safe commits that are not touching any critical code pieces. The final goal is to have #2457 in polkadot-staging - it'll should make bridges configuration much easier. So in next updates of polkadot-sdk and fellowship runtimes we'll decrease LOCs dedicated to bridges configuration.

All v2 stuff (dynamic lanes, relayers protocol) will stay in master.

Additionally, it'll make backporting easier - right now not having #2171 and #2181 in polkadot-staging is painful

* move Chain::ID from relay-level Chain to primitives-level Chain

* removed chain IDs from bp-runtime

* add missing file header
@svyatonik svyatonik added the A-chores Something that has to be done, as part of regular maintenance label Dec 27, 2023
* some code grooming: enable warn(missing_docs) for all piblic crates + added missing documentation + removed obsolete clippy/deny workarounds

* removed strange allow + added comment related to other allow

* removed incorrect_clone_impl_on_copy_type which is unknown to CI clippy
@svyatonik
Copy link
Contributor Author

Actually, there's a lot of changes that I'm going to port (#2457), so maybe it is better to have multiple PRs. So let's start with that one

@svyatonik svyatonik marked this pull request as ready for review December 28, 2023 08:01
@svyatonik svyatonik merged commit 8fb8fdd into polkadot-staging Jan 11, 2024
14 checks passed
@svyatonik svyatonik deleted the port-safe-commits-from-master branch January 11, 2024 09:39
serban300 pushed a commit to serban300/parity-bridges-common that referenced this pull request Mar 27, 2024
* introduce bp_messages::ChainWithMessages (paritytech#2171)

* Move Chain::ID from relay-level Chain to primitives-level Chain (paritytech#2181)

* move Chain::ID from relay-level Chain to primitives-level Chain

* removed chain IDs from bp-runtime

* add missing file header

* Some code grooming (paritytech#2276)

* some code grooming: enable warn(missing_docs) for all piblic crates + added missing documentation + removed obsolete clippy/deny workarounds

* removed strange allow + added comment related to other allow

* removed incorrect_clone_impl_on_copy_type which is unknown to CI clippy
serban300 pushed a commit to serban300/parity-bridges-common that referenced this pull request Apr 8, 2024
* introduce bp_messages::ChainWithMessages (paritytech#2171)

* Move Chain::ID from relay-level Chain to primitives-level Chain (paritytech#2181)

* move Chain::ID from relay-level Chain to primitives-level Chain

* removed chain IDs from bp-runtime

* add missing file header

* Some code grooming (paritytech#2276)

* some code grooming: enable warn(missing_docs) for all piblic crates + added missing documentation + removed obsolete clippy/deny workarounds

* removed strange allow + added comment related to other allow

* removed incorrect_clone_impl_on_copy_type which is unknown to CI clippy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chores Something that has to be done, as part of regular maintenance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants