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
I have a multisite config with targets. Using npx firebase-tools deploy --only hosting or npx firebase-tools deploy --only hosting:bbbb works fine. But if I use the new GitHub action, it fails on the line:
Running the same thing locally fails in the same way. The error is:
$ npx firebase-tools hosting:channel:deploy pr22-blah --only bbb --expires 30d --project blah-dev --json
{
"status": "error",
"error": "Hosting configs should only include either \"site\" or \"target\", not both."
}
Note that the command I used there adds --only bbb. The command fails the same way with or without that.
Also note that my firebase.json does NOT list "site" at all. See below:
I'm getting this error when not using channel but just firebase deploy --only hosting:. I'm running it on gitlab runner where I have site and target by branch name firebase deploy --only hosting:$CI_COMMIT_REF_SLUG -m "Tag $TAG Pipeline $CI_PIPELINE_ID, build $CI_BUILD_ID" --non-interactive
I have a multisite config with targets. Using
npx firebase-tools deploy --only hosting
ornpx firebase-tools deploy --only hosting:bbbb
works fine. But if I use the new GitHub action, it fails on the line:Running the same thing locally fails in the same way. The error is:
Note that the command I used there adds
--only bbb
. The command fails the same way with or without that.Also note that my
firebase.json
does NOT list"site"
at all. See below:.firebaserc:
firebase.json
[REQUIRED] Environment info
firebase-tools:.
npx firebase-tools --version
->8.14.0
Platform: OSX, but also GitHub Actions default image
[REQUIRED] Test case
See above.
[REQUIRED] Steps to reproduce
See above. Run the hosting:channel:deploy command
[REQUIRED] Expected behavior
It deploys
[REQUIRED] Actual behavior
(
--debug
flag adds a lot of HTTP logging noise at the front, but it's all 200s.)The text was updated successfully, but these errors were encountered: