heroku-buildpack-github-netrc icon indicating copy to clipboard operation
heroku-buildpack-github-netrc copied to clipboard

doesn't work

Open mateodelnorte opened this issue 7 years ago • 4 comments

-----> github-netrc app detected
       Generated .netrc & .curlrc files (available only at build-time)
/app/tmp/buildpacks/eeb32e6e6d5d4de74da7a5db6b6ecd56d059db9e34b150f0574844b853937897162815fa2429ab515bbf53c66a754091f086ed265408cc53634a034363efe95e/lib/github.rb:20:in `[]': no implicit conversion of String into Integer (TypeError)
	from /app/tmp/buildpacks/eeb32e6e6d5d4de74da7a5db6b6ecd56d059db9e34b150f0574844b853937897162815fa2429ab515bbf53c66a754091f086ed265408cc53634a034363efe95e/lib/github.rb:20:in `block in github_user_orgs'
	from /app/tmp/buildpacks/eeb32e6e6d5d4de74da7a5db6b6ecd56d059db9e34b150f0574844b853937897162815fa2429ab515bbf53c66a754091f086ed265408cc53634a034363efe95e/lib/github.rb:20:in `each'
	from /app/tmp/buildpacks/eeb32e6e6d5d4de74da7a5db6b6ecd56d059db9e34b150f0574844b853937897162815fa2429ab515bbf53c66a754091f086ed265408cc53634a034363efe95e/lib/github.rb:20:in `map'
	from /app/tmp/buildpacks/eeb32e6e6d5d4de74da7a5db6b6ecd56d059db9e34b150f0574844b853937897162815fa2429ab515bbf53c66a754091f086ed265408cc53634a034363efe95e/lib/github.rb:20:in `github_user_orgs'
	from /app/tmp/buildpacks/eeb32e6e6d5d4de74da7a5db6b6ecd56d059db9e34b150f0574844b853937897162815fa2429ab515bbf53c66a754091f086ed265408cc53634a034363efe95e/lib/github.rb:26:in `user_block'
	from /app/tmp/buildpacks/eeb32e6e6d5d4de74da7a5db6b6ecd56d059db9e34b150f0574844b853937897162815fa2429ab515bbf53c66a754091f086ed265408cc53634a034363efe95e/bin/compile:54:in `<main>'
 !     Push rejected, failed to compile github-netrc app.
 !     Push failed

mateodelnorte avatar Sep 08 '17 20:09 mateodelnorte

same issue

alexanderGalushka avatar Oct 05 '17 02:10 alexanderGalushka

Same here :/

thure avatar Oct 11 '17 16:10 thure

Any updates here? Or did you guys find an alternative solution?

danlutz avatar Sep 13 '18 15:09 danlutz

I ran into this error as well, and I was able to fix it by granting the following permissions to my auth token:

  • All "repo" permissions
  • "user > read:user" permission

CodingItWrong avatar Feb 14 '19 15:02 CodingItWrong