Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Top level 'runs:' section is required for annshiv/Hostinger-deployment/v2.1/action.yml #1

Open
SKbarbon opened this issue Jun 21, 2024 · 1 comment

Comments

@SKbarbon
Copy link

I have this issue:

Top level 'runs:' section is required for annshiv/Hostinger-deployment/v2.1/action.yml

And the action failed and nothing pushed to hostinger.

What I did

  1. I did generate SSH key, then stored it on deploy keys under deploy keys by name Hostinger key
  2. I did create a webhook, then pasted the webhook URL on it from the one I copyed from hostinger.
  3. I did create a publish.yml file, with content as following:
name: Generate a build and push to another branch

on:
  push:
    branches:
      - main # The branch name your are commit the new changes

jobs:
  build:
    runs-on: ubuntu-latest
    name: Build and Push
    steps:
      - name: Deploy to Hostinger
        uses: annshiv/[email protected]
        
      - name: git-checkout
        uses: actions/checkout@v3

      - name: Install all dependencies
        run: npm install

      - name: Build
        run: npm run build # The build command of your project

      - name: Push
        uses: s0/git-publish-subdir-action@develop
        env:
          REPO: self
          BRANCH: build # The branch name where you want to push the assets
          FOLDER: . # The directory where your assets are generated
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # GitHub will automatically add this - you don't need to bother getting a token
          MESSAGE: "Build: ({sha}) {msg}" # The commit message

Tell me whats wrong please

@codivist
Copy link

codivist commented Nov 1, 2024

I have the same setup and I'm getting the same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants