Skip to content
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

Merge failing with no useful message #4

Open
nanthony21 opened this issue Apr 16, 2021 · 4 comments
Open

Merge failing with no useful message #4

nanthony21 opened this issue Apr 16, 2021 · 4 comments

Comments

@nanthony21
Copy link

After pushing a very minor commit that definitely couldn't cause a merge conflict I am getting this as output:

[@octokit/rest] `const Octokit = require("@octokit/rest")` is deprecated. Use `const { Octokit } = require("@octokit/rest")` instead
merge main into privateMain
merge branch:main to: privateMain
Error: main merge failed: 

This action has been working fine for me up until today, not sure what changed.

@facundofarias
Copy link

Indeed, this one would be very helpful :)

@yechielb2000
Copy link

yechielb2000 commented Jan 25, 2023

Hi, I'm getting this message and I don't know how to solve this.
If you can help me it would be great, Thank you <3

Run mtanzi/action-automerge@v1
[@octokit/rest] `const Octokit = require("@octokit/rest")` is deprecated. Use `const { Octokit } = require("@octokit/rest")` instead
merge main into gh-pages
merge branch:main to: gh-pages
Error: main merge failed: Resource not accessible by integration

@kanumuruwe45
Copy link

Yes merging is failing
Run mtanzi/action-automerge@v1
[@octokit/rest] const Octokit = require("@octokit/rest") is deprecated. Use const { Octokit } = require("@octokit/rest") instead
merge dev into main
merge branch:dev to: main
Error: dev merge failed: Resource not accessible by integration

Do we have any update on this front?
Any leads is appreciated

@kanumuruwe45
Copy link

Nothing wrong from the actions, you just need to update the organization or Repo action settings like as below then it will work fine
Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

Under "Workflow permissions", choose GITHUB_TOKEN to have read and write access for all scopes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants