-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add luacheck and GitHub workflow #175
Comments
What? Who's setting up CI? |
You can set up CI with GitHub actions by adding a workflow. |
But... CI for what? Sorry, I'm all for CI, I'm just not sure where/how it's relevant right now. This isn't a code repo. |
No, I'm talking about Lua repositories. I created the issue here because this is a issue tracker repository. |
Oh, you're just suggesting that I set up some sort of basic style checking on the lua repos and forks I manage? I suppose I'm not against playing around w/ that; I've given up on doing any real sort of continuous testing on mod repos cuz I'd need to, like, mock a full instance of the game. I also run an IDE that runs a luacheck in real time while i edit the code... |
I suppose I'll add this to the bls_custom repo for experimentation |
@Panquesito7 any comments on what I'm doing wrong here? It's kvetching about docker, and I don't know why. https://github.com/BlockySurvival/bls_custom/actions/runs/32404553 |
The code has various warnings which need to be fixed. |
Does it? The only output I see is
|
https://github.com/BlockySurvival/bls_custom/runs/414134776 |
Now that it is working with |
I think you should go for it. I'd prefer to deal w/ the verbana mod myself, but feel free to put in PRs against the other repos we manage, and I'll set it up on the github side. |
I've created various PRs in various repositories. |
@Panquesito7 nice work 👍
@fluxionary you can still do integration-testing for the meta-repo. We are doing that for our For every commit a minetest-instance is started that checks if the engine starts and does some basic assertions: Background: the The CI-Tests even run when the Let me know if you need help setting that up... |
Thanks Buckaroo, that's really helpful. I can probably set it up myself sometime later when I get some energy. |
This is towards the top of my "high priority" list. Just need a few good days. |
I tried to whip up a PR for this a few days ago but had some issues:
Those aren't blockers but the repository can't be cloned 1:1 in a worldmods folder in the current state. I guess you are working with a |
Yes, we're using the main "mods" folder and a world.mt file to enable the mods; this allows admins to easily disable/enable mods, as well as individual submods from modpacks (and we very much do the latter). If there's something i can do to the REPOS folder & the associated symlink to make it work in a worldmods folder, w/out removing the current functionality, I'd love to hear it. Keep in mind that part of the problem is that the terumet mod's root isn't a proper mod folder itself. |
Also, I'm fairly certain a couple other mods require special lua libraries (e.g. |
We have a special case with the
You could of course just remove them at the start of the test script |
I'm working on refactoring things so that it'll work in either setup. Not feeling well rn though so it might be another while. |
@fluxionary there are some repositories (non-meta repos) that are still missing LuaCheck. |
I'm now working on to add LuaCheck for more repositories. 🙂 |
This issue is kinda old, but I still see a few repositories with no LuaCheck. |
fine by me. i've actually started using pre-commit, luacheck, and stylua in all my own projects, it certainly helps catch stuff. |
See GitHub Help for more information about GitHub actions.
You need to create and configure
.luacheckrc
in all repositories before adding the CI, otherwise you'll get a lot of (false) errors.If you don't know how to start, you can take inspiration from Cloud Items'
.luacheckrc
.The text was updated successfully, but these errors were encountered: