Site version

[ckenst]

1. I want to track each "deploy to production" which means I need some way to automatically tag and identify releases
2. This should be done as part of the CI system. Anything that gets merged into master (or better yet Switching from Master to Main #797 main) should get tagged with a release number and incremented

[ckenst]

This might end up being a site version that gets deployed to the site itself.

Summary of the Flow

1. You push changes to main.
2. The GitHub Action runs.
3. It reads the VERSION file (X), calculates the new version (X+1), and overwrites the file.
4. It builds your Jekyll site.
5. It automatically creates a new commit on main that only contains the updated VERSION file.
6. It deploys the entire site (including the new version number) to GitHub Pages.

[ckenst]

I've added the VERSION file and some other beginning things like where to put the VERSION in the footer in this commit 215a628

[ckenst]

Additional updates:

1. Version file is now in the _includes folder: https://github.com/TestingConferences/testingconferences.github.io/blob/main/_includes/VERSION.txt
2. This is then included in the footer using rev.{% include VERSION.txt %}.
3. The goal is still to increment the VERSION number on pushes to main. We want to read the VERSION file (X), calculate the new version (X+1). This way we can track all deployments and then take measurements (later) for each deployment.
4. We should also ensure every production deploy is tagged in Git to match the internal version.
5. Update the Roadmap to check off Automated Increments and Deployment Tagging