# Getting Started
# Beachball Workflow
First off, a
picture diagram is worth a thousand words, so here it is:
# Brief Description of Workflow
Without any configuration,
beachball fits into your workflow. When you have made some commits to your branch, simply fire up
beachball change to generate change files. During PR review and feedback loops, your colleagues might remind you to modify your change file descriptions or change type. This then gets merged to the target branch (e.g.
master). After this,
beachball publish is either called by a continuous integration (CI) system or manually by a developer. When this is called, three things happen:
All change files are deleted (more than one change file can be checked in before a single publish happens)
Versions are bumped, checked in locally and pushed remotely
npm packages are published to a public or private registry
At that point, your repo is ready for the next change!