8000 404 when firebase init and setup github workflow · Issue #8536 · firebase/firebase-tools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

404 when firebase init and setup github workflow #8536

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

Closed
alexandrefett opened this issue May 10, 2025 · 1 comment · Fixed by #8540
Closed

404 when firebase init and setup github workflow #8536

alexandrefett opened this issue May 10, 2025 · 1 comment · Fixed by #8540

Comments

@alexandrefett
Copy link

[REQUIRED] Environment info

Firebase-tools 14.3.1

Firebase-tools 14.3.1

Platform:
macOS

[REQUIRED] Test case

firebase init --debug
select hosting
folder: build/web
Rewrite HTML file: yes
Set the GitHub workflow? Yes
enter repo info (name/repository)
GET https://api.github.com/repos/undefined {"message":"Not Found","documentation_url":"https://docs.github.com/rest","status":"404"}

The workaround: downgraded firebase-tools to 14.2.1, everything worked as expected

[REQUIRED] Steps to reproduce

firebase init --debug
select hosting
folder: build/web
rewrite html file: yes
set github workflow? Yes
enter repo info (name/repository)
GET https://api.github.com/repos/undefined {"message":"Not Found","documentation_url":"https://docs.github.com/rest","status":"404"}

[REQUIRED] Expected behavior

retrieve the service account
set github secrets
write .firebasec

[REQUIRED] Actual behavior

Result from firebase init --debug
<! GET https://api.github.com/repos/undefined {"message":"Not Found","documentation_url":"https://docs.github.com/rest","status":"404"}

@aalej
Copy link
Contributor
aalej commented May 12, 2025

Thanks for reporting this and for sharing the error you encountered @alexandrefett! I was able to reproduce the issue. I'll raise this to our engineering team so they can take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0