Abandoned Action?

[ausfestivus]

Description

This action hasn't seen any updates in ~2 years. It feels like it is abandoned.

Reasons

I'm opening this FR to ask @mszostok if the project/Action is abandoned or not.

Im open to hearing from others who have found alternatives to this Action?

[mvdkleijn]

@ausfestivus As far as I can tell, there hasn't been a serious commit since October of '22. There was a single commit on a branch 8 months ago, but not from the repo owner.

This feels pretty dead to me. I'm tempted to fork it myself but not sure if I want the added maintenance load.

[martinm82]

Would be good to release a new version, especially after the GitHub App authentication was added in 0.7.4 but not in action.yml. This was done a bit later (ccda6cc).

[actuarysailor]

Anyone volunteering to take this action over? None of the forks look like they have done anything with it... https://github.com/mszostok/codeowners-validator/forks

Looking at the open issues, I agree this should support a pre-commit hook as well

[actuarysailor]

If you reference mszostok/[email protected] you can take advantage of his app input parameters

[mvdkleijn]

Anyone volunteering to take this action over? None of the forks look like they have done anything with it... https://github.com/mszostok/codeowners-validator/forks

Looking at the open issues, I agree this should support a pre-commit hook as well

Unfortunately I don't have the overhead necessary to take this on. Already working on a large project in the coming months.

[mszostok]

Hi all!

Thank you for your interest in this project! I truly appreciate it, and I apologize for the lack of recent updates.

When I first created this project, there was no support for CODEOWNERS validation on GitHub. Now, GitHub has introduced basic validation in the UI and via API, which addresses some initial gaps this project aimed to fill.

This project has always been a non-profit, open-source effort developed in my free time. Unfortunately, due to other commitments and priorities, I haven't been able to dedicate the time required for regular maintenance and new features. Here are some key points:

• The current feature set satisfies my personal use cases.

• Investing more time is risky, as GitHub could release a more comprehensive native solution at any moment.

  • They’ve already created a simple version, though it’s not integrated with CI.

• There are a lot of moving parts:

  • GitHub doesn’t always share their internal details or designs for certain things.
  • Adding a new feature like Enterprise SSO is another challenge.
    • I don’t have a setup to test this since I’m not part of any corporate accounts.

• Additionally, some non-functional tasks need to be done too:

  • improve the release pipeline
  • restructure it to allow easier extension (configuration, etc.)
  • enhance installation

  Without these, adding a new feature is problematic, and releasing a new version unnecessarily takes time, etc.

That said, I am open to reviving the project if at least one more person can join as a maintainer. Collaboration would help us decide on the next steps and split the efforts. I’d love to proceed with the steps outlined in #116.

If anyone is interested in joining me, please reach out here or contact me directly via email!