How to create the initial Home page in a repo Wiki via GitHub Actions?

[Violinist80]

Hi everyone.
I’m trying to create the very first page (Home.md) in a repository Wiki automatically from a GitHub Actions workflow. I can successfully publish artifacts and update files in the main repo, but I’m stuck at initializing the Wiki and committing the first page from an Action.

What I’ve tried:

Git push to the Wiki repo using a PAT or GITHUB_TOKEN:

• Clone https://github.com//.wiki.git
• Add Home.md if it doesn’t exist
• Commit and push

Permissions:

• Wiki is enabled in the repo settings.
• Tested with GITHUB_TOKEN (job-level permissions set to contents: read and write) and with an org secret PAT that has repo scope (including repo:status, repo_deployment, public_repo, repo:invite) and SSO authorized for the org.

Results:

• If the Wiki has never been manually created, the push sometimes fails or appears to succeed without creating the page.
• If I manually create the first page once, subsequent workflow runs can update it just fine.

Logs / symptoms
When the Wiki has never been initialized:

• fatal: repository 'https://github.com//.wiki.git/' not found (occasionally)
• Or push succeeds but the page isn’t visible.

Questions:

• Is there a known limitation that prevents Actions from creating the very first Wiki page if the Wiki was never initialized via the UI?

• Do I need a specific scope (or a different permission than contents: read and write) for pushing to .wiki.git?

• Is there a recommended API or Action to initialize the Wiki repo before the first push?

• If initialization is required once, is there a non-interactive way to do it purely from a workflow?

Any guidance, examples, or best practices are greatly appreciated. Thanks!

[ashmeet07]

This is a known, tricky limitation with GitHub Wikis: the .wiki.git repository does not exist until the Wiki is initialized by a user at least once via the GitHub UI. Your manual testing confirms this behavior.

Since there is no official API to force initialization, the only robust workaround is to use a Personal Access Token (PAT) with explicit permissions and a shell script that handles the "repository not found" error by running git init locally before the first push.

---

Recommended Solution: PAT and Initialization Script

Use a dedicated PAT and the following workflow steps. This script attempts to clone, and if it fails (meaning the Wiki is uninitialized), it initializes a local Git repository which can then perform the first push to the remote.

1. PAT and Secrets

• Token: Create a fine-grained PAT or a classic PAT with the repo scope enabled. This is crucial for cross-repo access and push permissions.
• Secret: Store this token as a Repository Secret named WIKI_PAT.

2. Workflow Implementation

Use the following job definition. It uses a robust shell script to handle both initialized and uninitialized Wiki states.

```yaml
jobs:
update_wiki:
runs-on: ubuntu-latest
permissions:
# Keep 'contents: write' for good practice, but PAT will handle Wiki auth
contents: write
steps:
- name: Checkout main repository code
uses: actions/checkout@v4

  - name: Configure Git for Wiki Push
    run: |
      git config --global user.name "github-actions[bot]"
      git config --global user.email "github-actions[bot]@users.noreply.github.com"
      
  - name: Clone or Initialize Wiki Repository
    run: |
      # 1. Prepare authenticated URL using the PAT
      WIKI_URL="https://${{ secrets.WIKI_PAT }}@github.com/${{ github.repository }}.wiki.git"
      WIKI_DIR="wiki"

      # 2. Attempt to clone (if already initialized)
      if git clone "$WIKI_URL" "$WIKI_DIR"; then
        echo "Wiki repo cloned successfully."
      else
        # 3. If clone fails (Wiki not found), initialize a local git repo
        echo "Wiki repo not found, initializing locally."
        mkdir "$WIKI_DIR"
        cd "$WIKI_DIR"
        git init
      fi
      
      # Change to the Wiki directory for operations
      cd "$WIKI_DIR"
      
      # 4. Create the Home page
      echo "# Home Page from GitHub Actions" > Home.md
      
      # 5. Stage, commit, and push
      git add .
      
      # Commit only if there are changes
      if ! git diff --cached --exit-code; then
        git commit -m "Auto-initialize/Update Home page via GitHub Actions"
        # Push using the authenticated URL. Wikis often require 'master'.
        git push "$WIKI_URL" master:master
        echo "Wiki successfully pushed."
      else
        echo "Home.md already up-to-date. Skipping push."
      fi
    env:
      WIKI_PAT: ${{ secrets.WIKI_PAT }}

```

[nwsparks]

this doesn't work. it will give a Repository not found error until the wiki is initialized by creating a page in the GUI first.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬