Skip to content

Disable renovating node version - #727

Merged
calebeby merged 2 commits into
v-nextfrom
renovate-node-version
May 21, 2020
Merged

Disable renovating node version#727
calebeby merged 2 commits into
v-nextfrom
renovate-node-version

Conversation

@calebeby

Copy link
Copy Markdown
Contributor

Tries to disable PR's like this: #690

I think this is the config we want: renovatebot/config-help#81 (comment)

@calebeby
calebeby requested review from a team and tylerstickaMay 20, 2020 18:05
@tylersticka
tylersticka removed their request for review May 20, 2020 18:43
Comment threadrenovate.json
{
"packageNames": ["node"],
"enabled": false
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this is saying:

  1. Find any package named "node"
  2. Apply the following special rules to it:
  3. The only special rule is to entirely disable renovate for it.

Is that right?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that is my understanding

@Paul-HebertPaul-Hebert left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@calebeby this code looks good to me.

Is there any way to test this without merging it? If not it might be good to get another pair of eyes on it. I know @spaceninja has some renovate experience.

@calebeby

Copy link
Copy Markdown
ContributorAuthor

No we don't have a way to test this until we merge it.

Here was my last shot at this: #689

narrator: it did not work

@calebeby
calebeby requested a review from spaceninjaMay 20, 2020 21:05
@Paul-Hebert

Copy link
Copy Markdown
Contributor

Cool, well the code looks good to me based on the linked issue and Renovate docs ¯\_(ツ)_/¯

I assume after we merge we just wanna keep an eye on Renovate to make sure it keeps acting correctly?

@calebeby

Copy link
Copy Markdown
ContributorAuthor

Yeah, should I merge or should I wait for @spaceninja to review?

@calebeby

Copy link
Copy Markdown
ContributorAuthor

After this is merged, I am expecting/hoping that this will auto-close: #690

@Paul-Hebert

Copy link
Copy Markdown
Contributor

Your call. I'm tempted to wait for @spaceninja 's review, but worst case this breaks renovate and not our actual codebase, so if you'd prefer to merge now that's fine with me

@spaceninjaspaceninja left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no way to evaluate this without trying it, but as Paul said, this won't break anything but Renovate, so go for it!

@calebeby
calebeby merged commit 94fe0a7 into v-nextMay 21, 2020
@calebeby
calebeby deleted the renovate-node-version branch May 21, 2020 19:57
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@calebeby@Paul-Hebert@spaceninja