Repository: scs/substrate-api-client (language: rust)

Issue:
Discuss: Switch polkadot branch naming to `release-polkadot-v1.x.x`
Parity now uses a different polkadot branch naming system: instead of `polkadot-v0.x.x` it's now `release-polkadot-v1.x.x`. I think it probably makes sense to follow parity in the new naming system with our branches as well.

@Niederb @masapr  what do you think?




Discussion / hints:
@haerdib I agree: I would also follow the naming system from polkadot. Otherwise it gets confusing 
I pushed the existing branches `polkadot-v1.x.x` with a new name `release-polkadot-v1.x.x`. I'd rather not remove the already pushed `polkadot-v1.x.x` branches. For the future, however, let's use only `release-polkadot-v1.x.x` branches.

Fix patch:
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index c974d8a86..9f940d378 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -3,9 +3,9 @@ name: Build & Test & Clippy
 on:
   workflow_dispatch:
   push:
-    branches: [ master, 'polkadot-v[0-9]+.[0-9]+.[0-9]+*' ]
+    branches: [ master, 'polkadot-v[0-9]+.[0-9]+.[0-9]+*', 'release-polkadot-v[0-9]+.[0-9]+.[0-9]+*' ]
   pull_request:
-    branches: [ master, 'polkadot-v[0-9]+.[0-9]+.[0-9]+*' ]
+    branches: [ master, 'polkadot-v[0-9]+.[0-9]+.[0-9]+*', 'release-polkadot-v[0-9]+.[0-9]+.[0-9]+*' ]
 
 env:
   CARGO_TERM_COLOR: always


Test patch: