Closed gabrielcsapo closed 7 years ago
@stackdot is anyone maintaining this repo?
Not actively, no
On October 21, 2016 at 4:48:21 PM, Gabriel Csapo (notifications@github.com) wrote:
@stackdot https://github.com/stackdot is anyone maintaining this repo?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/stackdot/NodeJS-Git-Server/pull/37#issuecomment-255461400, or mute the thread https://github.com/notifications/unsubscribe-auth/AAo3HLa94VBqbulHmfErHpIAvl0cYLFvks5q2SUVgaJpZM4Jj_f9 .
@qrpike would you be interested in moving this under someone who would be actively managing issues?
I would be willing to add you as a contributor if you like, giving you commit access.
@qrpike that would be great, could you provide NPM access as well?
@qrpike npm-username = gabrielcsapo
@gabrielcsapo seems you cant add access to a user npm module now, you have to create a npm org which costs $15/m. I guess just ping me when you need it pushed and I will push it for you. Would be even better if we could get the CI working again and have it auto publish through that only on successful changes.
@qrpike https://github.com/stackdot/NodeJS-Git-Server/pull/40 this fixes the CI issue.
adds async version to package.json
fixes #36