You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that this repository received zero maintenance in 2 years and @jesusvasquez333 seems to be inactive on github. This means that this action is at the high risk to become unusable at any moment.
If @jesusvasquez333 sees this, I would like to propose transfer of the action under an organization where there are multiple people that can step-in to fix it if needed. Once example could be https://github.com/coactions which I created some time ago specifically for this purpose.
Knowing current maintenance status I looked for alternatives but I was not able to find one that covers the same. I am aware that I could fork it and use that for or even publish the fork with another name but I do think that is better to join efforts on maintaining good code bits instead of spamming the marketplace.
The text was updated successfully, but these errors were encountered:
@ssbarnea did this get any traction behind the curtains? We (the tumbs) have been aware off the lack of maintenance as well. While we could fork this repo, the incentive behind coactions does take my likings.
Hello @ssbarnea , thank you very much for reaching out regarding this issue. Unfortunately I haven't been able to keep maintaining this repository. I would be more than happy to migrate this repository to an organization where more people can help with the maintenance.
It seems that this repository received zero maintenance in 2 years and @jesusvasquez333 seems to be inactive on github. This means that this action is at the high risk to become unusable at any moment.
If @jesusvasquez333 sees this, I would like to propose transfer of the action under an organization where there are multiple people that can step-in to fix it if needed. Once example could be https://github.com/coactions which I created some time ago specifically for this purpose.
Knowing current maintenance status I looked for alternatives but I was not able to find one that covers the same. I am aware that I could fork it and use that for or even publish the fork with another name but I do think that is better to join efforts on maintaining good code bits instead of spamming the marketplace.
The text was updated successfully, but these errors were encountered: