Hi all,

I've been doing a bit of cleanup on apertium-apy, and realized that Travis
hasn't been working for a while.

To solve for it, I did an initial integration with GithubActions.

I haven't spend too much time on it (Tino mentioned on IRC he's working on
a better CI for all modules) but I didn't want to allow merges with tests
failing.

I'd love if those of you who have more expertise on Apy could take a look
at this:

https://github.com/apertium/apertium-apy/pull/184

Other things I've seen not properly working on that repo:
- Pushes to dockerhub
- Pushes to Pypi?
- Not sure if with my changes I broke the code coverage check

If there are no objections, I'll probably merge it in the next couple of
days. Even if this is just an starting point, it should be already better
than what we had (no checks running at all)
-- 
< Xavi Ivars >
< http://xavi.ivars.me >
_______________________________________________
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to