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

Automerge patch not working? #720

Closed
rarkins opened this issue Aug 22, 2017 · 6 comments
Closed

Automerge patch not working? #720

rarkins opened this issue Aug 22, 2017 · 6 comments
Assignees
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:bug Bug fix of existing functionality

Comments

@rarkins
Copy link
Collaborator

rarkins commented Aug 22, 2017

Transferred from #473 (comment):

Another thing: "automerge": "minor" – shouldn't this automerge commits such as this one, instead of creating a PR?:

screen shot 2017-08-22 at 10 38 01

@rarkins rarkins added type:bug Bug fix of existing functionality priority-2-high Bugs impacting wide number of users or very important features ready labels Aug 22, 2017
@rarkins rarkins self-assigned this Aug 22, 2017
@rarkins rarkins mentioned this issue Aug 22, 2017
3 tasks
@rarkins
Copy link
Collaborator Author

rarkins commented Aug 22, 2017

I set up a test here: renovate-tests/automerge#10 using your renovate.json config and travis-ci

It behaved as following:

  • branch was created on run 1
  • PR was not created on run 1 as prCreation is set to "not-pending"
  • PR was created on run 2 after travis testing passed
  • PR was not automerged on run 2 as Travis added a new status check for the PR
  • PR was automerged on run 3 after travis went green again

@denkristoffer I notice in your repo that auth0-js is now up to 8.9.3. Did you merge that manually, or did renovate automerge it?

In your screenshot it shows 13 hours elapsed since the PR creation and still no automerge, so it looks like something was wrong.

There's a reasonable chance that whatever was wrong was fixed in this commit this morning: 2ca2e7c

@denkristoffer
Copy link

denkristoffer commented Aug 22, 2017

I merged it manually. I'll keep an eye on whether the commit this morning changed anything from here on.

@rarkins
Copy link
Collaborator Author

rarkins commented Aug 22, 2017

Ok, please reopen this issue if you find it happening again

@rarkins rarkins closed this as completed Aug 22, 2017
@denkristoffer
Copy link

denkristoffer commented Aug 22, 2017

It's happening again 🙂

This Pull Request updates dependency @​storybook/react](https://github.com/storybooks/storybook) from v3.2.5 to v3.2.6

I've left it unmerged.

Oh, is it possible that it's due to warnings? Since the workspace warning is always in the PR.

@rarkins rarkins reopened this Aug 23, 2017
@rarkins
Copy link
Collaborator Author

rarkins commented Aug 23, 2017

I think it's a config problem. I'm seeing:

"branch":"renovate/@storybook/react-3.x","level":30,"msg":"Pull Request #154 does not need updating"
"branch":"renovate/@storybook/react-3.x","level":20,"msg":"Checking #154 for automerge"
"branch":"renovate/@storybook/react-3.x","level":20,"msg":"No automerge"

I also found these log messages:

"msg":"No renovate.json found"
"msg": "Detected 2 package files: packages/website/package.json,package.json"
"packageFile":"packages/website/package.json","msg":"No renovate config"
"packageFile":"package.json","msg":"Found package.json renovate config"
"packageFile":"packages/website/package.json","depType":"devDependencies","dependency":"@storybook/react"

It looks like you have 2 package.json files but the config is in only one of them. Therefore any config you specify will be applied only to packages in that package.json and not to the other one. In theory we might be able to add some "overrideRepoConfig: true" option in future that lets one package.json specify the behaviour for all package files, but that's not supported today. You will need to either copy/paste the config into the second package.json, or into a renovate.json file in the root of the repo.

@rarkins rarkins added priority-4-low Low priority, unlikely to be done unless it becomes important to more people review and removed priority-2-high Bugs impacting wide number of users or very important features ready labels Aug 23, 2017
@denkristoffer
Copy link

Oh indeed, the renovate config is only in my root package.json, I just assumed that it would apply to the whole repository when placed there. I'll add the config to the different packages and see if that fixes it 👍

@rarkins rarkins closed this as completed Aug 23, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:bug Bug fix of existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants