mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-26 05:17:58 +00:00

T

Svyatoslav Nikolsky acd043bc5f Remove bridges zombienet tests from CI (#3071 )

closes https://github.com/paritytech/parity-bridges-common/issues/2796

This partially reverts the #2439 - there are some changes (unrelated to
CI) that we still want to keep. The reason of that removal is that with
async backing enabled for Rococo AH (and for other chains in the near
future), we see a lot of issues there (because we run `14` nodes +
additional standalone process within a same container and it causes a
lot of timeouts). There's no way known to me to fix it right now, so
we're removing those tests hopefully temporarily to keep CI green

2024-01-26 12:45:23 +00:00

.cargo

Set clippy lints in workspace (requires rust 1.74) (#2390 )

2023-12-13 15:11:07 +01:00

.config

Bump lycheeverse/lychee-action (#2900 )

2024-01-15 21:07:09 +00:00

.github

Review: Remove audit rules (#3010 )

2024-01-22 10:12:58 +01:00

.gitlab

Remove bridges zombienet tests from CI (#3071 )

2024-01-26 12:45:23 +00:00

bridges

Various nits and alignments for testnet runtimes (#3024 )

2024-01-23 22:51:47 +00:00

cumulus

Add RadiumBlock collectives-westend bootnode (#3044 )

2024-01-25 11:37:43 +00:00

docker

Remove bridges zombienet tests from CI (#3071 )

2024-01-26 12:45:23 +00:00

docs

Bump docify from 0.2.6 to 0.2.7 (#3036 )

2024-01-24 17:33:28 +00:00

polkadot

Remove duplicate subsystem-bench from Cargo.toml (#3073 )

2024-01-26 10:55:38 +00:00

prdoc

Add NonFungibleAdapter (#2924 )

2024-01-26 08:23:19 +00:00

scripts

Adds missing feature flags in UI Test update script (#3015 )

2024-01-22 11:50:07 +00:00

substrate

rpc-v2/tx: Rename transaction to transactionWatch (#3040 )

2024-01-25 17:07:44 +00:00

.gitignore

Move developer-hub to polkadot-sdk-docs (#2598 )

2023-12-05 10:23:24 +01:00

.gitlab-ci.yml

[ci] Remove unused jobs (#2502 )

2024-01-11 11:30:17 +00:00

.prdoc.toml

PRDoc new schema (#1946 )

2023-12-04 14:25:57 +00:00

.rustfmt.toml

Update fmt file and some authors (#1379 )

2023-09-04 09:19:41 +02:00

BRIDGES.md

Update bridges subtree (#1392 )

2023-09-11 11:47:45 +03:00

Cargo.lock

bump reed-solomon-novelpoly version (#3065 )

2024-01-26 10:13:53 +00:00

Cargo.toml

Remove duplicate subsystem-bench from Cargo.toml (#3073 )

2024-01-26 10:55:38 +00:00

README.md

Update rust docs link in README.md (#2794 )

2023-12-25 22:13:29 +01:00

README.md

NOTE: We have recently made significant changes to our repository structure. In order to streamline our development process and foster better contributions, we have merged three separate repositories Cumulus, Substrate and Polkadot into this repository. Read more about the changes here.

Polkadot SDK

The Polkadot SDK repository provides all the resources needed to start building on the Polkadot network, a multi-chain blockchain platform that enables different blockchains to interoperate and share information in a secure and scalable way. The Polkadot SDK comprises three main pieces of software:

Polkadot

Implementation of a node for the https://polkadot.network in Rust, using the Substrate framework. This directory currently contains runtimes for the Polkadot, Kusama, Westend, and Rococo networks. In the future, these will be relocated to the runtimes repository.

Substrate

Substrate is the primary blockchain SDK used by developers to create the parachains that make up the Polkadot network. Additionally, it allows for the development of self-sovereign blockchains that operate completely independently of Polkadot.

Cumulus

Cumulus is a set of tools for writing Substrate-based Polkadot parachains.

Upstream Dependencies

Below are the primary upstream dependencies utilized in this project:

Security

The security policy and procedures can be found in docs/contributor/SECURITY.md.

Contributing & Code of Conduct

Ensure you follow our contribution guidelines. In every interaction and contribution, this project adheres to the Contributor Covenant Code of Conduct.

Additional Resources

For monitoring upcoming changes and current proposals related to the technical implementation of the Polkadot network, visit the Requests for Comment (RFC) repository. While it's maintained by the Polkadot Fellowship, the RFC process welcomes contributions from everyone.