Can I publish multiple branches of a repository on GitHub Pages?

[AnkitaSood]

I have already published the master branch of my repo on Github Pages. Can I somehow publish another branch of the same repository so the the url is something like: username.github.io/repositoryname/branch ? Or will I have to create another repository instead of a branch to publish it?

[birdcar]

Hi @ankitasood! 

Can I somehow publish another branch of the same repository so the the url is something like: username.github.io/repositoryname/branch ? Or will I have to create another repository instead of a branch to publish it?

GitHub Pages only lets you configure one publishing source for a particular repository. So in this particular case, you’ll need to create a new repository and add the content you’d like to publish with GitHub Pages to that newly created repository.

Does that answer your question? Please let me know if I misunderstood you or you have additional questions. 

[zabojad]

Hi there!

It’s a pity it works that way. In my case, I am maintaining an open source project hosted on GitHub. The project has several major versions (few of them still supported and maintained separately on different branches of the repo). It would be very nice if I could have the documentation of each of those versions/branches published separately.

Best,

Thomas

[Vadorequest]

Exactly, also it’s doesn’t help when working on documentation because you can’t preview what will be build on the github doc site until it’s merged into master…

What I’d prefer, is to automatically build one doc site for each branch that have a docs/ folder, and use either subdomains or a different domain for docs generated from branches that aren’t the default branch (usually “master”)

Example:

https://unlyed.github.io/next-right-now/ (“master” branch)

https://unlyed-docs.github.io/next-right-now/  (“docs” branch)

https://docs.unlyed.github.io/next-right-now/ (“docs” branch)

I think the latest looks the cleanest.

It could be done either automatically for all branches, or through a pattern (v*, for all v1, v2 branches and such) or enabled branch by branch.  Pattern allows for automation and would reduce maintainance/configuration.

This would be much more usable.

[ChildishGiant]

I’m using github pages for my master branch but netlify for the dev branch, as they allow hosting for seperate branches.

[MichaelHabib]

Hi,
Github pages does NOT allow a separate website or even section per branch, but I want to bring your attention to a free open source solution that does : https://antora.org/

[vokhidovhusan]

@ankitasood thank you for the question and @nickcannariato thank you for the answer

[djmacloud]

Maybe this help:

https://medium.com/geekculture/when-youre-working-on-a-static-site-and-github-pages-feels-like-the-perfect-hosting-solution-a41c37f4e326

[axherrm]

As a workaround to deploy multiple branches of my angular project, I created the following workflow:

name: Continuous Deployment

on:
  push:
    branches:
      - "**"

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write
  actions: read

# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
concurrency:
  group: "pages"
  cancel-in-progress: true

jobs:
  build_matrix:
    runs-on: ubuntu-latest
    outputs:
      json_branches: ${{ steps.generate-matrix.outputs.json_branches }}
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - name: Generate Matrix
        id: generate-matrix
        run: |
          branches=($(git branch -r | cut -c 3- | sed 's/origin\///g'))
          json_branches=$(printf '%s\n' "${branches[@]}" | jq -R . | jq -s -c .)
          echo "json_branches=${json_branches}" >> $GITHUB_OUTPUT

  build:
    runs-on: ubuntu-latest
    name: Build
    needs:
      - build_matrix
    strategy:
      matrix:
        branch: ${{ fromJSON(needs.build_matrix.outputs.json_branches) }}
    steps:
      - uses: actions/checkout@v4
        with:
          ref: ${{ matrix.branch }}
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - name: Build
        run: |
          npm install
          npm run build
      - uses: actions/upload-artifact@v3
        with:
          name: ${{ strategy.job-index }}
          path: dist/cv/browser/

  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    needs:
      - build_matrix
      - build
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - name: Setup Pages
        uses: actions/configure-pages@v3
      - run: gh run download ${{ vars.GITHUB_RUN_ID }} --dir branches
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

      - name: Create public folder
        run: |
          mkdir public
          mv .github/workflows/index.html ./public/index.html
          cd public
          branches=$(echo '${{ needs.build_matrix.outputs.json_branches }}' | jq -r '.[]')
          i=0
          for branch in ${branches}
          do
            mkdir -p -- $branch
            mv ../branches/$i/* ./$branch

            echo "<li><a href=\"./CV/${branch}\">${branch}</a></li>" >> index.html

            i=$((i+1))
          done
          cat ../.github/workflows/index_suffix.html >> index.html
          ls -lR
      - name: Upload artifact
        uses: actions/upload-pages-artifact@v2
        with:
          path: ./public/
      - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v2

The workflow runs on a push on every branch, which then updates the deployment of all branches.
I'm aware of the poor performance of this, espacially when lots of branches exist, but in my case with mostly only 2-3 branches this is not a big problem.
Also, I'm aware of the problem that one branch build failing means breaking the build of all branches (this could possibly be fixed, but I didn't intend to do it).
In the first job, a json array of all branch names gets created, which then is used for matrix in die build job, so that each branch has its own build job.
The results of the build job are then uploaded as artifact and in the last job downloaded to deploy them to GitHub Pages.

Again, I'm aware of the poor performance of this, but it enables a pretty workflow overview like this:

[VeraVechy]

Thanks so much 👍 I appreciate your response. This helps.

…

On Wed, 17 Jan 2024, 17:48 Yuhesh Pandian P J, ***@***.***> wrote: There could be several reasons for CSS not reflecting on your deployed site. Check if the CSS file paths are correct, clear browser cache, and ensure there are no errors in the CSS code. If the issue persists, inspect the browser's console for error messages, which can help pinpoint the problem. — Reply to this email directly, view it on GitHub <#21582 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEVSFUZUI2Y3YLRZHIUGVVDYO76GJAVCNFSM6AAAAAA6ITD3ACVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCNJZGMZDO> . You are receiving this because you commented.Message ID: ***@***.***>

[ghost]

Your Welcome ☺️

[tobenot]

Based on the above answer, I adopted the approach of committing multiple branches to files in my other repository, and then deploying them all together to GitHub Pages from that repository. This way, I can access the content of the main branch in /main, the content of the dev branch in /dev, and deploy an index page in the root directory.
Thank you very much for the answer above! It solved my problem~

基于上面的回答，我采用了将多个分支commit到我的另一个仓库的文件下，然后在另一个仓库全部一起部署到github pages上的方式，这样就可以在那个仓库的/main里面取到main分支的内容，/dev取到dev分支的内容。根目录可以部署一个索引页。

非常感谢上面的回答！解决了我的问题~