Deploy rustdoc on GA (paritytech#2)

* Deploy rustdoc on GA

* Update README.md

.github/workflows/rustdoc.yml

@@ -0,0 +1,51 @@
+name: Rustdoc
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+    - main
+
+concurrency:
+  group: rustdoc-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+env:
+  CARGO_INCREMENTAL: 0
+  CARGO_NET_RETRY: 10
+  RUSTUP_MAX_RETRIES: 10
+
+jobs:
+  rustdoc:
+    runs-on: ubuntu-22.04
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install Protoc
+        uses: arduino/setup-protoc@v3
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Configure cache
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.cargo/registry
+            ~/.cargo/git
+          key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.toml') }}
+          restore-keys: |
+            ${{ runner.os }}-cargo-
+
+      # Build the rust crate docs
+      - name: Build Documentation
+        run: cargo -Zgitoxide -Zgit doc --all --no-deps --lib
+        env:
+          RUSTDOCFLAGS: "-Z unstable-options --enable-index-page"
+
+      - name: Deploy Docs
+        uses: JamesIves/github-pages-deploy-action@v4
+        with:
+          branch: gh-pages
+          folder: target/doc

README.md

@@ -1,6 +1,7 @@
 # Subcoin: Bitcoin Full Node in Substrate
 
 [![Continuous integration](https://github.com/subcoin-project/subcoin/actions/workflows/ci.yml/badge.svg)](https://github.com/subcoin-project/subcoin/actions/workflows/ci.yml)
+[![Rustdoc](https://github.com/subcoin-project/subcoin/actions/workflows/rustdoc.yml/badge.svg)](https://github.com/subcoin-project/subcoin/actions/workflows/rustdoc.yml)
 
 > [!WARNING]
 >

crates/pallet-bitcoin/src/lib.rs

@@ -2,7 +2,7 @@
 //!
 //! This pallet is designed to be minimalist, containing only one storage item for maintaining the state
 //! of the UTXO (Unspent Transaction Output) set by processing the inputs and outputs of each Bitcoin
-//! transaction wrapped in [`Pallet::Call::transact`]. There is no verification logic within the
+//! transaction wrapped in [`Call::transact`]. There is no verification logic within the
 //! pallet, all validation work should be performed outside the runtime. This approach simplifies
 //! off-runtime execution, allowing for easier syncing performance optimization.