renovatebot / app-support

Discussion/support issues for the hosted Renovate App
0 stars 0 forks source link

PR not opened for a new repo #3

Closed piotr-s-brainhub closed 5 years ago

piotr-s-brainhub commented 5 years ago

What Renovate type are you using? Renovate GitHub App?

Describe the bug

Did you see anything helpful in debug logs?

DEBUG: Returning closed PR list comments
DEBUG: Ensuring comment "Renovate is disabled" in renovatebot/renovate#122
DEBUG: Comment is already update-to-date
INFO: Repository is disabled - skipping

Expected behavior A PR updating dependencies should be opened.

Additional context Many months ago I closed the initial renovate PR but its comment says:

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.

So after pushing renovate.json, renovate should be re-enabled.

My renovate.json:

{
  "automerge": false,
  "commitMessagePrefix": "[renovate] ",
  "labels": [
    "renovate"
  ],
  "npmToken": "<redacted>",
  "rangeStrategy": "bump",
  "packageRules": [
    {
      "automerge": true,
      "automergeType": "pr-comment",
      "groupName": "DMX dependencies",
      "managerBranchPrefix": "",
      "packagePatterns": [
        "^@dmx/"
      ],
      "schedule": "at any time"
    },
    {
      "automerge": true,
      "automergeType": "pr-comment",
      "groupName": "DMX dependencies",
      "managers": [
        "circleci"
      ],
      "managerBranchPrefix": "",
      "schedule": "at any time"
    },
    {
      "allowedVersions": "1.13.0",
      "packageNames": [
        "yarn"
      ]
    },
    {
      "groupName": "mongoose",
      "managerBranchPrefix": "mongoose",
      "packageNames": [
        "mongoose"
      ],
      "rangeStrategy": "pin",
      "schedule": "at any time"
    },
    {
      "allowedVersions": "10.16.0",
      "packageNames": [
        "node"
      ]
    }
  ],
  "groupName": "other than DMX",
  "schedule": "before 3am on the first day of the month"
}
rarkins commented 5 years ago

This should now be resolved. The repo was classified as 'disabled', which means it's no longer queued regularly. I updated this manually and triggered a new job, which succeeded.

piotr-s-brainhub commented 5 years ago

thanks