Does not trigger github workflow after auto update merge
See original GitHub issueHi there, our required workflow doesn’t get triggered after autoupdate. It says Expected - Waiting for status to be reported
. Look at the attachment.
![Screen Shot 2022-07-18 at 1 33 05 PM](https://user-images.githubusercontent.com/51537954/179612445-01c499b1-df52-46a7-93e9-a9ee7d6fb96b.png)
Here’s our autoupdate.yaml file
name: autoupdate
on:
pull_request:
types: [auto_merge_enabled]
jobs:
autoupdate:
name: autoupdate
runs-on: ubuntu-18.04
steps:
- uses: docker://chinthakagodawita/autoupdate-action:v1
id: autoupdate
env:
GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
MERGE_CONFLICT_ACTION: 'fail'
- run: echo 'Merge conflicts found!'
if: ${{ steps.autoupdate.outputs.conflicted }}
- run: echo 'No merge conflicts'
if: ${{ !steps.autoupdate.outputs.conflicted }}
Here’s our beginning of not triggered workflow yaml file if you want to see events that suppose to trigger the workflow. Any idea?
name: Build
on:
push:
pull_request:
types: [opened]
jobs:
test:
...
build:
Issue Analytics
- State:
- Created a year ago
- Comments:5
Top Results From Across the Web
Auto-merge will not trigger other workflows · Issue #111 - GitHub
I'm using this action to auto-merge https://github.com/dependabot/fetch-metadata#enabling-auto-merge and it's working fine except that the ...
Read more >Merge by github action does not trigger CI that listen by branch
The expectation I want is invoke the CI action after merge-staging-in-to-master was done. There is my code below. merge-staging-in-to-master.yml
Read more >GitHub Actions workflows for automatic rebasing and merging
This workflow is triggered by adding a label called rebase to your pull request. It uses the automatic-rebase action to perform the rebase,...
Read more >7 Github Actions Tricks I Wish I Knew Before I Started
The workflow will trigger on every pull request to the main branch. Not ... This will usually happen after a pull request was...
Read more >My GitHub Actions workflows are not starting - Robs blog
The cause of this is that scheduled runs only trigger from the default branch (main). Several triggers behave this way, like a Pull...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Using Personal Access Token triggers the subsequence workflows. Thanks @Julian88Tex
Created a feature request discussion to hopefully get GitHub to make this a bit clearer: https://github.com/github-community/community/discussions/21091