Interesting use of
hererocks by the way, I've never seen that. It looks cleaner than the Lua rigging we have for sile.
I'm going to make a reusable action for it
this is what I have so far: https://github.com/leafo/lua-twitter/blob/a6b514735492bd3404ccbccf74dd80e81268a9cf/.github/workflows/test.yml
Thanks for pointing that out @leafo. That's quite a bit of tooling though! I'm hoping some of that gets extracted to a reusable action that can live outside of my repository ;-) I have a working Travis setup now. I think I'm going to wait on implementing Actions until there is something with a little less plumbing to debug and maintain.
for travis I've always used this: https://github.com/moteus/lua-travis-example
I'm familiar with that setup and use it too but again it's a lot of tooling to include in the parent repository and changing any part of it involves a lot of round trip trial-and-error with Travis.
is there a changelog for the new release ? couldn't find any specific in changelog.md. Also it doesn't appear in https://luarocks.github.io/luarocks/releases/
I'm done with my GitHub actions for Lua and LuaRocks:
https://github.com/marketplace/actions/install-lua
https://github.com/marketplace/actions/install-luarocks
https://github.com/marketplace/actions/install-lua
https://github.com/marketplace/actions/install-luarocks
Here's an example of a test suite using them: https://github.com/leafo/lua-twitter/blob/master/.github/workflows/test.yml
Thanks @leafo! I set those actions up on simoncozens/cassowary.lua#7 and it appears to work great (At least in my fork, I guess PR's don't work in Actions until it's been started on master?).
I don't happen to think that was a good idea, but it does still exist.
Also @leafo I see you are posting to Lua Locks after build. Have you set this up to handle releases when Github tags are created as well or are you just using it for updating SCM versions?
github marketplace needs 1 action per repo, so there's
leafo/install-lua and leafo/install-luarocks
oh
I see what's going on.. https://github.com/marketplace/actions/install-lua-luajit
they generated a new url because I changed the title of the action to mention luajit
that's annoying (especially since they don't create redirects)
well, in any case the name used in the workflow won't change
@leafo Thanks again, I just started a new project fluent-lua and it was nice to get going quickly and cleanly with actions.
I'm looking into how to post to Lua Rocks now though, and it looks like even in your lua-twitter project example you are posting the same spec twice for every run, no? Shouldn't that bit be a separate job (depending on the first) so it doesn't repost the spec for every iteration of the matrix?
that was just me messing around. I think the only thing missing for deploy from tag is generating a rockspec with the correct version in the name and file
You should only need to change your scm rock if you add/remove files; or change the URL of your repository
*scm rockspec
alerque: when I do my releases I make a "release branch"; commit the release (with updated NEWS file, renamed rockspec, version file in repository filled in); tag that commit; then merge it back into master (where rockspec is still scm one)
First the vast majority of the content is duplicated over and over again in mulpiple files just to change one key (the version). Some projects rename the file on each release, but that makes it hard to track the history, and also it blocks people from installing old versions. Those that don't rename end up with a bunch of clutter, often in the root of the repo, hence why a directory just for accumulating specs seemed like the most sensible thing I've seen.
And what are the prerequisites to start contributing to Lua? I'm just a beginner right now. So can someone help me out?