From 68cc6e683fe9312ac8371b20198ffd48ae38bba9 Mon Sep 17 00:00:00 2001
From: Yuki Hattori <15963767+yuhattor@users.noreply.github.com>
Date: Sun, 18 Jun 2023 00:32:46 +0000
Subject: [PATCH] Update link

---
 .../gitbook-staging-branch-deploy.yml         | 30 +++++++++++++++++++
 ...-guests-writing-contributing-agreements.md |  2 +-
 2 files changed, 31 insertions(+), 1 deletion(-)
 create mode 100644 .github/workflows/gitbook-staging-branch-deploy.yml

diff --git a/.github/workflows/gitbook-staging-branch-deploy.yml b/.github/workflows/gitbook-staging-branch-deploy.yml
new file mode 100644
index 0000000..122736b
--- /dev/null
+++ b/.github/workflows/gitbook-staging-branch-deploy.yml
@@ -0,0 +1,30 @@
+name: Gitbook Staging Branch Deploy
+
+on:
+  push:
+    branches:
+      - "staging"
+
+jobs:
+  gitbook-generation:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        book: [Home, Getting-Started-with-InnerSource, Understanding-the-InnerSource-Checklist]
+    steps:
+    - uses: actions/checkout@v3
+      with:
+        ref: staging-${{ matrix.book }}
+    - name: Merge branch into the book's branch
+      uses: mtanzi/action-automerge@v1
+      with:
+        github_token: ${{ github.token }}
+        source: 'staging'
+        target: staging-${{ matrix.book }}
+    - name: Copy .gitbook.yml to root
+      run: cp books/${{ matrix.book }}/.gitbook.yaml .
+    - name: Commit updated files for the book
+      uses: stefanzweifel/git-auto-commit-action@v4
+      with:
+        commit_message: Writing updated files for the book
+        branch: staging-${{ matrix.book }}
diff --git a/books/Understanding-the-InnerSource-Checklist/5-creating-good-house-rules-for-guests-writing-contributing-agreements.md b/books/Understanding-the-InnerSource-Checklist/5-creating-good-house-rules-for-guests-writing-contributing-agreements.md
index a2c7196..07e2130 100644
--- a/books/Understanding-the-InnerSource-Checklist/5-creating-good-house-rules-for-guests-writing-contributing-agreements.md
+++ b/books/Understanding-the-InnerSource-Checklist/5-creating-good-house-rules-for-guests-writing-contributing-agreements.md
@@ -19,7 +19,7 @@
   
 <!-- TCs cannot be forced to accept and take ownership of broken code, code without proper tests, undocumented code, or even code that doesn’t meet their style standards. Contributing agreements are a way to formalize the responsibilities of the developers on the originating side of the code. -->
 
-## コントリビューション協定とは何か<a href="#what-is-contribution-agreement" id="#what-is-contribution-agreement" />
+## コントリビューション協定とは何か<a href="#what-is-contribution-agreement" id="#what-is-contribution-agreement" ></a>
 
 トラステッドコミッターは、_コントリビューション協定_ を記述して所有します。
 コントリビューション協定があることでハウスルールは明確になり、コードによるコントリビューションをトラステッドコミッターが受け入れるために必要なことをコントリビューターに知らせることができます。