Next step · What to do next

Run build and tests automatically on every push (CI)

What you may see

I want a warning before broken code reaches the live site

Why this step

A small automatic job that builds and tests each change keeps the main branch always working.

Before you start

Do build and tests pass locally with one command each?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Run build and tests automatically on every push (CI)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
A small automatic job that builds and tests each change keeps the main branch always working.

DO THESE STEPS, IN THIS ORDER
1. Create a minimal workflow that installs from the lock file, builds, type checks, lints and runs tests on every pull request, with the same Node version as the host.
2. Use secrets only by name, with test keys, never live ones; cache dependencies; keep the job under a few minutes.
3. Turn on branch protection so the main branch needs a green check, and explain how to read a failure.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A deliberate break in a branch turns the check red and blocks the merge; a fix turns it green.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not store secrets in the workflow file.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Create a minimal workflow that installs from the lock file, builds, type checks, lints and runs tests on every pull request, with the same Node version as the host.
Use secrets only by name, with test keys, never live ones; cache dependencies; keep the job under a few minutes.
Turn on branch protection so the main branch needs a green check, and explain how to read a failure.

Do not do this

Do not skip checks "just this once".
Do not store secrets in the workflow file.

Try another entry