See discussion on GitHub
https://github.com/wikimedia/texvcjs/pull/34#issuecomment-583995995
I would be in favor of just enabling Travis for github.com/wikimedia/texvcjs and make use of the existing pipeline, which is IMHO good enough for what we are doing.
@Pchelolo already tried to enable Travis but he does not seem to have permissions either.
Description
Event Timeline
I'm seeing if I can enable Travis for that repo. However they seem to have changed the process and it's a bit of messy right now.
Mentioned in SAL (#wikimedia-releng) [2020-02-15T21:33:48Z] <hauskatze> GitHub: Activated Travis CI at https://travis-ci.org/wikimedia/texvcjs for https://github.com/wikimedia/texvcjs per https://github.com/wikimedia/texvcjs/pull/34 and T245344
@Physikerwelt I think I have enabled back tests via the legacy Travis CI integration page. I think this is being deprecated in favour of GitHub actions which I'm not familiar with though. The current PR is not being tested. I created a draft test PR and it started to build so I guess if you want https://github.com/wikimedia/texvcjs/pull/34 checked you'll need to amend the patch to trigger a build, unless there's another way.
@MarcoAurelio thank you. Works great.
@Jdforrester-WMF for me Travis works fine. But if most people prefer GHActions we can also migrate to that service. I am flexible in this regard. However, I have a preference for self-serviced CIs.