64bitpandas / amethyst

📓 obsidian-compatible notes theme for hugo, built from quartz and hugo-book
https://amethyst.bencuan.me
MIT License
116 stars 96 forks source link

Having a deployment bug #8

Open voidmain443 opened 4 months ago

voidmain443 commented 4 months ago

Describe the bug A clear and concise description of what the bug is. I chage all step of the workflow and push the code but the deployment is show me the error about the Jekyll.? I don't want to use Jekyll that is why I use Hugo. but the deployment code is not show the Jekyll but the rendering is show me the layout of the error of Jekyll.

Can you help me ?

To Reproduce Steps to reproduce the behavior:

name: Deploy to GitHub Pages

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 0    # Fetch all history for .GitInfo and .Lastmod

      - name: Build Link Index
        uses: jackyzha0/hugo-obsidian@v2.18
        with:
          index: true
          input: content
          output: assets/indices
          root: .

      - name: Setup Hugo
        uses: peaceiris/actions-hugo@v2
        with:
          hugo-version: '0.96.0'
          extended: true

      - name: Build
        run: hugo --minify

      - name: Deploy
        uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: ./public
          publish_branch: deploy  # deploying branch
          cname: voidmain443.github.io

Expected behavior it have to be publish but it is doesn't.

Screenshots If applicable, add screenshots to help explain your problem. image

it is different here that the Jekyll is not on the official docs .

image

image

Desktop (please complete the following information):

Additional context Add any other context about the problem here.

64bitpandas commented 2 months ago

Hi! I took a look at your fork, and it seems like there are two workflows running. The one you probably wanted to run looks like it was successful and you should be able to view your built site on the deploy branch.

I'm not sure where this Jekyll workflow is coming from, but it should be safe to ignore (or delete, if you can figure out why it is running).

foreverStudent001 commented 1 month ago

Hi, it might help to change the source to GitHub Actions instead of building your site from the main branch. Also, you can check in settings > actions > general at what you have under Actions Permissions. This is what mine looks like: image

Hope it helps! ~