You just learned how to create a branchβthe first step in the GitHub flow.
Branches are an important part of the GitHub flow because they allow us to separate our work from the master branch. In other words, everyone's work is safe while you contribute.
Tips for using branches
A single project can have hundreds of branches, each suggesting a new change to the master branch.
The best way to keep branches organized with a team is to keep them concise and short-lived. In other words, a single branch should represent a single new feature or bug fix. This reduces confusion among contributors when branches are only active for a few days before theyβre merged π into the master branch.
Trying to use the latest release results in the following error message: File not found: '/home/runner/work/_actions/JasonEtco/rss-to-readme/v1.2.0/dist/index.js'
Looking at the Actions tab, building v1.2.0 has an error.
I'm opening this issue due to a failure that is happening in my Repo for no reason, I've set up the workflow to work the same way as you described in the Readme file.
I'm sure there's something I've configured incorrectly, but the scheduled build fails every night with the error
Error: No commit found for the ref master
β fatal HttpError: No commit found for the ref master
at /home/runner/work/_actions/JasonEtco/rss-to-readme/v1/dist/index.js:19081:21
at processTicksAndRejections (internal/process/task_queues.js:97:5)