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
Hi! I wrote the pronto-slim_lint runner a while ago for my own purposes, but I haven't been able to keep it up to date with newer Pronto releases. Others have asked to get access to maintain it, so I was wondering if it would be possible to move the repository into the prontolabs organization, so that others would be able to help maintain it. I expect that ultimately some of the folks asking to contribute to that runner might need to be the ones actually contributing and keeping it up to date, but I figured it would be better for it to be in a community organization where multiple people have access rather than a handful of people disconnected from the broader community. Thank you!
Concretely, I am guessing that we'd need to move the repository and also grant rubygems publish access to some others (or maybe a CI system?).
The text was updated successfully, but these errors were encountered:
ibrahima
changed the title
Request to move pronto-slim_lint runner
Request to move pronto-slim_lint runner repository into prontolabs
Feb 16, 2022
Hi! I wrote the pronto-slim_lint runner a while ago for my own purposes, but I haven't been able to keep it up to date with newer Pronto releases. Others have asked to get access to maintain it, so I was wondering if it would be possible to move the repository into the prontolabs organization, so that others would be able to help maintain it. I expect that ultimately some of the folks asking to contribute to that runner might need to be the ones actually contributing and keeping it up to date, but I figured it would be better for it to be in a community organization where multiple people have access rather than a handful of people disconnected from the broader community. Thank you!
Concretely, I am guessing that we'd need to move the repository and also grant rubygems publish access to some others (or maybe a CI system?).
The text was updated successfully, but these errors were encountered: