-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action doesn't merge a bump from the correct target #18
Comments
hmmm interesting, can you share your workflow file and your |
I believe upgrade to latest ( |
Thanks @ahmadnassri It's interesting to not that it the action got upgraded to 2.0.1 and not 2.0.4 by dependabot yesterday. Not too sure when you released v2.0.4 but maybe something to look into. |
they were all released in sequence on the same day possibly, your dependabot config has a max number of PRs per day / week etc ... or it just derped 🤷♂️ regardless, that's a dependabot question I cannot answer |
I also had a run where I got messaged with "manual merging required". Upgrading the action from v1 to v2 helped. Here is my final config: /.github/workflows/ci.yml - name: 'Automerge dependency updates from Dependabot'
uses: ahmadnassri/action-dependabot-auto-merge@v2
# Guarantee that commit comes from Dependabot (don't blindly trust external GitHub action checks)
if: github.event_name == 'pull_request' && github.actor == 'dependabot[bot]'
with:
github-token: ${{ secrets.GH_TOKEN }} /.github/auto-merge.yml - match:
dependency_type: all
update_type: 'semver:major' /.github/dependabot.yml version: 2
updates:
- package-ecosystem: npm
directory: '/'
schedule:
interval: weekly
pull-request-branch-name:
separator: '-'
target-branch: master
commit-message:
prefix: chore
include: scope
labels:
- "type: chore \U0001F9F9" |
Hello,
I've moved to the v2.0.1 of your action and I'm getting now this strange behaviour.
The target is set to minor, however when it finds a minor upgrade it doesn't merge it and says
manual merging required
.Could you please let me know what's wrong?
The text was updated successfully, but these errors were encountered: