add renovate configuration to Repository if repository is in @octokit

[gr2m]

No description provided.

[oscard0m]

I added some missing logic to @octoherd/script-setup-renovate. I think we are ready to run this across the repos of the org you would like to have Renovate.

I noticed it creates/updates .json removing the new lines and spaces completely, is this a blocker to our use-case? (see octoherd/script-setup-renovate#29)

➡️ fixed here

The script requires a token with privileges to push directly on the defaultBranch branch. @gr2m

---

Pending to do the removal of pkg.renovate entry from package.json. I'm assuming .github/renovate.json will take precedence according to Renovate Documentation.

➡️ Octoherd script ready to remove the entries from package.json 🍾 octoherd-script-remove-renovate-package.json/

[gr2m]

So there are two things we need to do, if I get it correctly

1. move the renovate configuration in current @octokit repositories from the package.json files to .github/renovate.json (as we just did in @probot)
2. Create a .github/renovate.json file when running npm init octokit-project and creating a @octokit repositor (this is the original scope of this issue)

Did I get this right?

I can run the scripts to conclude step 1 if everything is ready @oscard0m

[oscard0m]

So there are two things we need to do, if I get it correctly

1. move the renovate configuration in current @octokit repositories from the package.json files to .github/renovate.json (as we just did in @probot)

2. Create a .github/renovate.json file when running npm init octokit-project and creating a @octokit repositor (this is the original scope of this issue)

Did I get this right?

I can run the scripts to conclude step 1 if everything is ready @oscard0m

The steps are correct and the scripts are ready 🚀 .

[gr2m]

I updated all @octokit repositories. Only thing left now is

Create a .github/renovate.json file when running npm init octokit-project and creating a https://github.com/octokit repositor (this is the original scope of this issue)

[github-actions]

🎉 This issue has been resolved in version 2.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀