mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #244] Support running Azure Pipelines #168
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#168
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 @fwilhe on GitHub (May 17, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/244
Hi @cplee
this is a suggestion where I would like if it is worth doing it. The basic idea is to extend the scope to also allow execution of azure yaml pipelines.
Why do I think this would be worth it?
This could potentially be very useful for developers in such orgs, maybe even a source for new contributors.
Rough list of things that would need to be supported (I did not research this, just off the top of my head):
Any opinions?
I can't promise anything, but I would be open to contributing to this feature if it is accepted.
@cplee commented on GitHub (May 18, 2020):
This is a great idea @fwilhe - not sure if it helps, but i wrote a blog on the similarities here: https://www.liatrio.com/blog/github-actions
@github-actions[bot] commented on GitHub (Jul 18, 2020):
Issue is stale and will be closed in 7 days unless there is new activity