question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Auto Merge fails on initial try

See original GitHub issue

The action runs on checksuite-success. It retries three times and fails on each. Doing a dependabot recreate triggers automerge correctly, and the rebasing of other open dependabot prs closes other PRs successfully too.

It fails on with the following error message:

Run ridedott/dependabot-auto-merge-action@master
Found pull request information: {"reviewEdges":[{"node":{"state":"APPROVED"}}]}.
##[error]An unexpected error occurred: (e || "").replace is not a function, TypeError: (e || "").replace is not a function
    at escapeData (evalmachine.<anonymous>:1:65447)
    at Command.toString (evalmachine.<anonymous>:1:65373)
    at issueCommand (evalmachine.<anonymous>:1:64866)
    at Object.issue (evalmachine.<anonymous>:1:64935)
    at Object.error (evalmachine.<anonymous>:1:91320)
    at Object.t.pullRequestHandle (evalmachine.<anonymous>:1:117513)
    at processTicksAndRejections (internal/process/task_queues.js:93:5).
##[error]Node run failed with exit code 1

What are the expected results?

It should work on initial try.

What are the actual results?

PRs are not properly merged on the initial try, but the Checksuite is all green. It retries 3 times and then fails. Rebasing or recreating the PR with dependabot recreate in chat resolves the issue as shown in the pr example below.

How much does it hurt?

Telling Dependabot to recreate takes as long as merging with admin privileges. Therefore the action does not smooth anything when this bug occurs.

Further Links:

An example failing Action and the corresponding failing example PR.

The Action YML Is the default.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:3
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
merlinnotcommented, Feb 5, 2020

@Twonki @nuria-fl @hiwelo I merged two PRs: fix to the logging mechanism and better setup/configuration instructions (see the Readme). Let me know what the results are.

0reactions
lapplislazulicommented, Feb 7, 2020

Just wanted to confirm that the issue seems to be resolved.

Thank you very much for the quick fix 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Git says "Automatic merge failed", what does it mean?
It means that Git cannot automatically determine how to merge the two branches. Git is asking you to do the merge manually, and...
Read more >
Git Troubleshooting. Automatic merge failed; fix conflicts… - gkzz
1st step is to see the files affected by the merge conflict. · $ git status. You have unmerged paths. (fix conflicts and...
Read more >
Resolving merge conflicts in Git - genomewiki
If your merge failed to even start, there will be no conflicts in files. If git finds conflicts during the merge, it will...
Read more >
Automatic merge failed; fix conflicts and then commit the result
Auto - merging README.mdCONFLICT (content): Merge conflict in README.mdAutomatic merge failed ; fix conflicts and then commit the result.
Read more >
How To Handle Merge Conflicts (Automatic merge failed
For discounts on courses I offer, see the 2020 trailer video of this YouTube channel - https://www.youtube.com/watch?v=RJyHb45efUs.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found