mirror of
https://github.com/nektos/act.git
synced 2026-04-27 01:45:52 +03:00
[GH-ISSUE #1490] How to ignore GitHub Page #768
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#768
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MathieuSoysal on GitHub (Dec 3, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1490
Details
Introduction
I'm currently contributing to a GitHub project.
For this, I'm writing a GitHub workflow inside a GitHub Action that tests the creation of JavaDoc files.
This workflow should be run with act.
The project of the GitHub Action when I want to add this GitHub Workflow: https://github.com/MathieuSoysal/Javadoc-publisher.yml
Problem
The problem, when I execute my GitHub workflow with act I obtain this error.
GitHub Workflow
My GitHub Workflow :
GitHub Action
The GitHub Action of the project: https://github.com/MathieuSoysal/Javadoc-publisher.yml/blob/main/action.yml
Command
The executed command to run nektos/act :
actQuestion
Does someone know how we can say to nektos/act to ignore the deployment phase? It is possible?
@almereyda commented on GitHub (Jun 11, 2024):
Hi @MathieuSoysal, you had closed this issue.
Did you find a resolution to skip GitHub Pages actions with act?
Eventually the regression could be included in https://nektosact.com/not_supported.html
Could we reopen here? Now that GitHub Pages have switched to CI-only build workflows based on GitHub Actions, this may be more important again.