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
`The current project directory '${this.cachedProjectRoot||"<NO PROJECT DIRECTORY FOUND>"}' does not exist. Please use the 'update_firebase_environment' tool to target a different project directory.`,
Your goal is to deploy resources from the current project to Firebase.
27
+
28
+
Active user: ${accountEmail||"<NONE>"}
29
+
Active project: ${projectId||"<NONE>"}
30
+
31
+
Contents of \`firebase.json\` config file:
32
+
33
+
\`\`\`json
34
+
${config.readProjectFile("firebase.json",{fallback: "<FILE DOES NOT EXIST>"})}
35
+
\`\`\`
36
+
37
+
## User Instructions
38
+
39
+
${prompt||"<the user didn't supply specific instructions>"}
40
+
41
+
## Steps
42
+
43
+
Follow the steps below taking note of any user instructions provided above.
44
+
45
+
1. If there is no active user, prompt the user to run \`firebase login\` in an interactive terminal before continuing.
46
+
2. If there is no \`firebase.json\` file and the current workspace is a static web application, manually create a \`firebase.json\` with \`"hosting"\` configuration based on the current directory's web app configuration. Add a \`{"hosting": {"predeploy": "<build_script>"}}\` config to build before deploying.
47
+
3. If there is no active project, ask the user if they want to use an existing project or create a new one.
48
+
3a. If create a new one, use the \`firebase_create_project\` tool.
49
+
3b. If they want to use an existing one, ask them for a project id (the \`firebase_list_projects\` tool may be helpful).
50
+
4. Only after making sure Firebase has been initialized, run the \`firebase deploy\` shell command to perform the deploy. This may take a few minutes.
51
+
5. If the deploy has errors, attempt to fix them and ask the user clarifying questions as needed.
52
+
6. If the deploy needs \`--force\` to run successfully, ALWAYS prompt the user before running \`firebase deploy --force\`.
53
+
7. If only one specific feature is failing, use command \`firebase deploy --only <feature>\` as you debug.
0 commit comments