diff options
| author | Deniz Akşimşek <deniz@denizaksimsek.com> | 2022-05-17 09:25:50 +0300 |
|---|---|---|
| committer | Deniz Akşimşek <deniz@denizaksimsek.com> | 2022-05-17 09:25:50 +0300 |
| commit | b75200a4dbb3e16ef9e13d2332885f35c22ea259 (patch) | |
| tree | 16976fea6e860d1c0885870eede0174f3fb495f5 | |
| parent | 06b0d07bb3b8efce62771282e3a8cdbe40799164 (diff) | |
| download | missing-b75200a4dbb3e16ef9e13d2332885f35c22ea259.tar.gz missing-b75200a4dbb3e16ef9e13d2332885f35c22ea259.zip | |
dev note: "Idea for branching structure"
| -rw-r--r-- | dev-notes | 20 |
1 files changed, 20 insertions, 0 deletions
@@ -1,4 +1,24 @@ +2022-05-17 + +Idea for branching structure: + +No `master` or `main` branch. Different projects use the default branch for +different purposes, which can be confusing. I don't want people to need to read +stuff just to send a PR. + +The default branch is called `dev`. This means the default branch is the right +place to open PRs. + +There is a `prod` branch, which is what's deployed to Netlify. To release a new +version, make a git tag and move the prod branch to it. In addition, +documentation fixes can be made directly against the prod branch. + +Feature branches probably won't be used much, and most development will be +directly on the dev branch. This is because of the difficulty of merging CSS. + +-- dz4k + 2022-05-17 |