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
Hello again #1489
Comments
@simov you're an owner on the request org now, and you have publish access to most of the npm packages that live in the org (I had access to all except This may help if someone needs to do the same in the future: #!/bin/sh
org=request
user=simov
curl -s https://api.github.com/users/$org/repos | grep '"name"' | cut -d'"' -f4 | while read repo; do
package=`curl -s https://raw.githubusercontent.com/$org/$repo/master/package.json | grep '"name"' | cut -d'"' -f4`
if [ ! -z "$package" ]; then
echo "Adding user $user to npm package $package (gh:$org/$repo) ..."
npm owner add $user $package
echo
fi
done |
Thanks @nylen that's great responsibility idd. I think we should be ready for a new release next week. |
@simov Any specific tasks that need to get done for the next release? I'd be happy to help out if possible. |
@froatsnook I can't think of anything specific atm, except that I'll fix #1477 Once that's in, I'll make major refactoring on the readme, mostly UX related, as discussed here #1340 Since I'm not seeing anything that urgent atm, and because every PR needs time to be reviewed, I estimated the release day to be the next week. Of course that's only what I'm seeing, if you want to improve or add something, feel free to do so 👍 |
I've got a filter now that will trigger if you @nylen ping me on GitHub. Otherwise I can't make any promises. |
I've been trying to get back to
request
for a while now and haven't been able to do much. I'm cleaning out a few issues in other projects in our org today though.Does anyone need anything like a new version released, or access to release versions? Anywhere else I can provide a good amount of help in a short time?
The text was updated successfully, but these errors were encountered: