Skip to content

Commit 14c6fed

Browse files
authored
Update 2022-08-12-workflows-not-starting.md
1 parent cb31fe1 commit 14c6fed

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

_posts/2022-08-12-workflows-not-starting.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,9 @@ I have ran into this myself and looked for 15 minutes before I saw what was wron
3030
3131
It needs to be stored in the following folder: `/.github/workflows/`. And that folder is `workflows` (plural) and **not** `workflow` (singular).
3232

33+
## Next, pushing with a user?
34+
If you make changes within a workflow and did not set any user information (a Personal Access Token or with a GitHub App, more info [in this post](blog/2022/01/03/GitHub-Tokens)), then you are using the GitHub Actions Bot (a GitHub App under the covers), that creates a default GITHUB_TOKEN that can have write access to your repository. GitHub has built in that this token **never triggers a workflow run**, to prevent an endless loop of actions triggering workflows, that write files, create issues, or something else, and then trigger another actions run.
35+
3336
## Scheduled runs not starting
3437
When you add your first schedule for a daily run, you might be surprised that it does not start at the schedule you have set. You might scratch you head and wait for a couple of days, and nothing will happen.
3538

0 commit comments

Comments
 (0)