mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #874] Enhancement: Alternate or unified API to accomodate Gitlab #521
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#521
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 @drschwabe on GitHub (Nov 13, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/874
This maybe not necessarily a feature since perhaps the initiatve would be better spearheaded as sep project entirely (and perhaps hosted on Gitlab) but anyway the idea is to offer an 'act' equivalent but for Gitlab's CI/CD jobs/pipeline API
I love act and nothing wrong with Github Actions, but when a project comes up and is hosted on Gitlab that kinda makes this tool & expertise around it unavailable.
@catthehacker commented on GitHub (Nov 13, 2021):
GitLab runner allows local execution of CI/CD (it's not hard to set up), I'm not aware if it has dry-run but there isn't much priority to pursue this.
@drschwabe commented on GitHub (Nov 15, 2021):
Okay cool, thanks for clarifying - I will look into setting up GitLab runner
@drschwabe commented on GitHub (Nov 15, 2021):
related discussion:
https://stackoverflow.com/questions/32933174/use-gitlab-ci-to-run-tests-locally
@catthehacker commented on GitHub (Nov 15, 2021):
Although once all our issues with GitHub are fixed, this can be reconsidered :)
@mon-jai commented on GitHub (Jun 17, 2023):
+1 for this.