Push Build Verify

Steps

0. Context: Run tau --json current. If the user asked for a new project in this session, confirm Project matches that name (see taubyte-orchestrator → New project hard gate) before any push or import.

1. Pre-push build/runtime config check:

   • Validate .taubyte/build.sh and .taubyte/config.yaml for changed functions/websites/libraries.
   • Ensure required env vars are declared when server-side config is needed.
   • For Go functions, confirm sources follow taubyte-go-sdk-constraints: empty.go at function root only (no manual lib/, no hand-written main.go). Optional local WASM check: taubyte/go-wasi Docker recipe in that skill.

2. If website/library was newly created in this workflow, import first:

   tau import website --name <website>
   tau import library --name <library>
   

   • Run only for resources that exist and are relevant to this workflow.

3. Push project config:

   tau push project --config-only --message "<message>"
   

4. Wait for the Config build to finish (required):

   Website/library pushes can depend on resources being present in config. After a config push, do not push website/library code until the latest Config build is ✔ success (or fails).

   # poll until the latest Config row shows ✔ (success) or × (failed)
   tau query builds --since 1h
   
   # if failed, inspect logs and fix config before continuing
   tau query logs --jid <config_job_id>
   

5. Check jobs/logs (capture IDs/diagnosis in context log):

   tau query builds --since 1h
   tau query logs --jid <job_id>
   

6. Push project code:

   tau push project --code-only --message "<message>"
   

7. Website/library repositories (only after config build success):

   • Preferred:

     tau push website --name <website> --message "<message>"
     tau push library --name <library> --message "<message>"
     

   • Exception-only fallback for website/library repos:

     git add .
     git commit -m "<message>"
     git push origin main
     

8. Re-check builds/logs and update context log.

Push policy guardrails

• For project config/code (tau push project), never bypass failures with git; fix tau/root cause first.
• Git fallback is allowed only for website/library repo-local push path when tau website/library push is unavailable or unsupported.
• If git fallback is used, record reason in context log.
• Always record relevant build/job IDs and latest log diagnosis in context log after checks.