Repository navigation
Home
This repo is so I can gain experience using GitHub Flow. Therefore, I will delete the two branches staging and production. The only long-lasting branch is main. All other branches will be short lived feature or bug branches.
There are going to be three environments:
- development
- staging
- production
This is the first real iteration of using 3 GitHub Workflow files and one branch. The 3 GitHub Workflow files are:
- workflow-1.yml
- workflow-2.yml
- workflow-3.yml
And of course, just the main branch.
Due to the logic in each of the GitHub Workflow files, they all ran when I committed them, because the logic would run the YAML files on a push.
- staging
- development
- Make a branch rule for the
developmentbranch to run workflow-1.yml - Make a branch rule for the
stagingbranch to run workflow-2.yml - Make a branch rule for the
productionbranch to run workflow-3.yml
Because this repo is now down to only one long-lived branch (main), these branch rules are irrelevant.
I made it so that a reviewer is required. Since I am the only one with write permissions to the repo, I made myself the reviewer.
As of 6/11/2026 this repo has only two YAML files:
- single-workflow-release.yml
- single-workflow.yml
This workflow will launch two jobs, one to work with the Development environment, and the other to work with the Staging environment. They work fine but note that they both run. At someone's suggestion in the GitHub Action forum, I put in a needs for the staging-deploy step. However, it doesn't delay pausing the staging-deploy step. What I believe it does is make staging-deploy wait for development-deploy to run first, then staging-deploy runs. So, not bad, but note that both jobs run.
This GitHub workflow also works but note that it is triggered by creating a new Release in the GitHub.com web interface! It does not work by a PR being created.