📣 LOOKING FOR MAINTAINERS 📣

[sammcj]

If anyone is interested to helping to maintain this project - please comment on this issue.

@sbe-arg and myself been added as contributors because it went unmaintained for some time - it's not our creation, it's very much a community project.

One of the major problems is the lack of reasonable test coverage (see #184), which is in part why we suggest people don't run it from main/master unless you're happy to be testing cutting edge changes.

We're only two folks, in the same time zone so it's currently very much a best effort as we both work full time and have social lives etc... so if you want to help out with testing, bug fixes and peer reviews - leave a comment here!

[fabricepipart]

Hi
I saw your request for some help on the CI. I'll try to see if I find the time to give some help on that front.

[miguelaferreira]

I've used this action for quite some time now and plan to continue to use it. I'm happy to help out maintaining it.

[sammcj]

That's fantastic, thank you @miguelaferreira!

@anothrNick could you please add @miguelaferreira to the repo maintainers?

[beholdenkey]

Hey Awesome tool, would love to help keep it going for others.

[sammcj]

Hey @beholdenkey 👋 - that's great to hear.

Something this project desperately needs is some good tests so folks can have confidence before accepting or requesting changes on PRs.

Do you think that's something you could help get started? If so - perhaps you could either submit a few PRs relating to #184.

[beholdenkey]

@sammcj Sounds good, let me take a look.

[beholdenkey]

@sammcj here is a pretty big pull request let me know your thoughts on the changes - #252

[sammcj]

Awesome stuff @beholdenkey - really appreciate the effort that's gone into that! ❤️ I've added a few comments - nothing major at all other than a suggestion to add some tests given it's a big PR 😄

[sbe-arg]

This is just a reminder that we are still looking for maintainers that are regular to contributing and not just one off pr proposals.

What we have learned so far is we need more and more testing pre and post releases specially during big refactors and drastical new feature additions.

As result we see a big flow of issues for the missing scenarios created after each release and this makes it hard to keep usability consistent if releases are created by someone that does not check back if suckh changes have created impacted other users.

Ill continue to support this action for the foreseeable future.

[Kshitij-Dhakal]

Hello

[jcvegan]

Me!