For my first test of GitHub Actions, I created a branch gh-actions-test in a repository, copied the default template workflow file into the directory .github/workflows as test.yml, and pushed the branch to GitHub.
Now I would immediately expect to see this workflow in the “Actions” tab, but no such luck. OK, maybe it needs another push to be really kicked off? So I committed a dummy file to the repository, pushed this, and… still nothing in the “Actions” tab.
The only way I can make this workflow visible in the “Actions” tab is to merge my branch to master, and thus have one particular version of the files in the .github/workflows directory in master.
if true that workflow .yml files are only picked up from the most recent commit in master, then this would mean that any development on the workflow files themselves can only happen in master, and that CI steps can not evolve on other branches. Nor would I be able to add workflows on branches.
This seems like a very serious limitation, so I find it hard to believe. For example, with Azure Pipelines, the required azure-pipelines.yml file is picked up *on* each branch, *for* each respective branch.
So: How do I develop (and debug) my workflows outside of master?