Closed saniales closed 4 years ago
@saniales we have always used CircleCI or Azure DevOps, depending on the workflow. Is there any specific reason for which you'd suggest to move to GH actions? BTW, I'm not opposed to it. I've always had to find some time to dig more into it. For now, Circle has always done what we've asked for and we have good templates around for it, already used in other repos...
@saniales you can find the config for this repo here: https://github.com/italia/publiccode-validator/blob/master/.circleci/config.yml
@LucaPrete my bad I did not see it, I just saw circleCI did not trigger on my fork and I wasn't able to verify how to have #9 fixed.
I opened #14 just because I did not see the file, you can choose what to do with it ;)
honestly it is so simple as a workflow that I would keep it in any case as an additional one (and an excuse to experiment with github actions, since they can be written in forks and are automatically bound by github)
Additional Note: if you merge this it includes #12 (again, my bad)
closed by #14
I suggest creating A Github Action to validate the code
reference: https://github.com/features/actions