Separate build and deploy for creating a PDF such that a new branch requirement is enforced for releases of CV, per #2. Adds minimal documentation in the README for this.

Author: aridyckovsky

.github/workflows/create-pdf.yml

@@ -2,9 +2,9 @@ name: Create PDF
 
 on:
   push:
-    branches: [ main ]
+    branches: [ main, drafting ]
   pull_request:
-    branches: [ main ]
+    branches: [ main, drafting ]
   workflow_dispatch:
 
 jobs:
@@ -28,6 +28,11 @@ jobs:
           name: cv
           path: cv/cv.pdf
           compression-level: 0 # don't compress PDF
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    if: github.ref == 'refs/heads/main'
+    steps:
       - name: Tag
         id: generate_release_tag
         uses: amitsingh-007/next-release-tag@v5.1.0

README.md

@@ -15,6 +15,10 @@ TODO.
 
 TODO.
 
+## Development
+
+Changes take place in the `drafting` branch. The `main` branch serves as the latest stable and released version of the CV, including its contents and the methods for generating it. When a CV draft is ready for release, make a pull request to merge the draft into `main`. If all checks pass, complete the merge to build and release a new version of the CV. Versions are formatted with `v{yyyy}.{mm}.{dd}.{i}`, e.g., [v2024.5.4.1](https://github.com/aridyckovsky/cv/releases/tag/v2024.5.4.1). Multiple versions within a day are tracked by an increasing sequence of natural numbers `i`.
+
 ## Acknowledgements
 
 This automation is made possible with the help of great open source contributiosn like: