Team Workflows

6

questions

Describe GitHub Flow.

main is always deployable. For each task — a short branch from main, regular commits and pushes, a Pull Request with review and green CI, merge into main and deploy. The branch is deleted after the merge.

How is Git Flow different from GitHub Flow?

GitHub Flow has one permanent branch, main, and short feature branches — built for continuous deploy. Git Flow has two permanent branches (main for releases, develop for integration) plus release/* and hotfix/* — built for planned, versioned releases. It's more complex but gives control over what goes into a release.

What do you check during code review?

That the change does what it claims and doesn't break anything nearby; readability and standards (WPCS); security — sanitizing, escaping, nonces, capability checks; query performance; tests. I write comments concretely, with a suggestion, and mark nitpicks as optional.

When should you use squash merge?

When the branch's intermediate commits ("fix typo", "wip") have no value for history: squash turns the PR into one meaningful commit in main. Not when the PR contains several separate logical changes that are useful to see and revert individually.

Which model would you pick for an online store with frequent releases, and why?

GitHub Flow: frequent releases need a short path from task to production, and develop plus release branches only add merges and delays. Risks are covered by CI, review, feature flags and quick rollback.

Why must main always be deployable?

Because it's deployed at any moment, and new branches and hotfixes start from it. If main is broken, the whole team is blocked. So only verified code gets into main — through PR, review and CI.