Why hard fork from nektos/act

[mengzhuo]

I'm downstream Alpine package maintainer of act, I'm curious why and furture plans of this project

[ChristopherHX]

TLDR I always had a fork with unmerged changes most of the time with broken tests on my private account, on the other hand this version has the test suite working similar to the original

During the last years we had more maintainers working on nektos act, this changed for a while now.

IMHO I am the only one left, who wrote code without being able merge code changes in a reasonable time frame. Batched mass merges that happend sometimes are prone to errors and merge conflicts.

Since I shifted my focus to the Gitea Project a possible future is to make this the new gitea/act, e.g. replace the gitea only fork with this one that has original tests running.

Initial work of having tests running on both gitea.com and gihub.com: #145, redundancy of Source Control providers.

---

This version of act is pretty unknown and contains breaking changes that I do not see to fit into nektos/act were it would be too time consuming for me to integrate them.

[mengzhuo]

Thanks for explaination, I think it's better to setup a new package instead of changing current act package for Alpine