Question

A maintainer needs to make several experimental changes to a documentation site over the next week. The main branch is used for automatic production deployments and must always remain stable and releasable. What is the recommended way to organize this work so production is never disrupted while the changes are in progress?

Accepted Answer

Create a new branch off main, commit the experimental changes there, and only merge into main when the work is complete and reviewed

Answer

Commit each experimental change directly to main and revert them one by one if production breaks

Answer

Delete the main branch temporarily and recreate it after the experimental work is finished

Answer

Create a separate repository for the experiments and manually copy files back into the original repository afterward