-
Notifications
You must be signed in to change notification settings - Fork 11
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
Looking for maintainers! #550
Comments
I'll merge a couple of PRs in the coming days and cut a release to confirm everything works fine for me :) |
@jbwheatley do you have an idea why PR checks seem to not run for PRs coming from forks? I believe there's a setting to enable in the project settings to allow them (I don't have access to that). |
Its supposed to ask for an approval to run them, but I'm not getting that button :( |
might actually have some time this weekend to do some more handover/maintenance. Wish me luck :) |
@jbwheatley ideally I'd like to have access to the project secrets to be able to define new ones (I wouldn't be able to read existing ones anyway, at least not that easily). The use case I have in mind is to use Renovate. Currently it works only partially (doesn't suggest PR for workflows, is unable to detect previous PRs closed...) because it uses a token with limited scopes that you had set for other usages I believe. Other than that, no issue so far. I'm able to keep up for simple maintenance. I'm not sure I'll be able to provide much more than that unfortunately :( But it's not like there was a ton of daily issue or PRs to review :) |
From what I can see online you should be able to add secrets as a collaborator :( |
I could create a more permissive token |
I don't have access to the "Settings" tab at all. Not sure why 🤷🏼♂️ |
As mentioned in #549, I no longer feel able to maintain this project by myself. Let me know here if you'd like to be considered as a collaborator. @gaeljw has already generously volunteered. I'll try to do what I can to allow y'all to keep this project alive and updated in my absense.
The text was updated successfully, but these errors were encountered: