james/gcode
1
0
Fork 0
Code Issues Pull requests Projects Releases 7 Packages Wiki Activity

Configure Renovate #3

Merged
jimsy merged 0 commits from renovate/configure into main 2021-01-04 22:19:26 +13:00
Conversation 2 Commits - Files changed -
jimsy commented 2021-01-02 18:49:46 +13:00 (Migrated from gitlab.com)
Copy link

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.

Detected Package Files

  • .gitlab-ci.yml (gitlabci)
  • mix.exs (mix)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding MR is merged
  • Separate major versions of dependencies into individual branches/MRs
  • Do not separate patch and minor upgrades into separate MRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise MRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all MRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit MR creation to a maximum of two per hour
  • Limit to maximum 20 open MRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Ignore spring cloud 1.x releases
  • Use semantic prefixes for commit messages and MR titles
  • If semantic commits detected, use semantic commit type chore for all

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Merge Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This MR has been generated by Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin. 🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged. --- ### Detected Package Files * `.gitlab-ci.yml` (gitlabci) * `mix.exs` (mix) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding MR is merged - Separate major versions of dependencies into individual branches/MRs - Do not separate patch and minor upgrades into separate MRs for the same dependency - Upgrade to unstable versions only if the existing version is unstable - Raise MRs immediately (after branch is created) - If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others - Keep existing branches updated even when not scheduled - Disable automerging feature - wait for humans to merge all MRs - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories - Autodetect whether to pin dependencies or maintain ranges - Rate limit MR creation to a maximum of two per hour - Limit to maximum 20 open MRs at any time - Group known monorepo packages together - Use curated list of recommended non-monorepo package groupings - Ignore spring cloud 1.x releases - Use semantic prefixes for commit messages and MR titles - If semantic commits detected, use semantic commit type <code>chore</code> for all 🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the `renovate.json` in this branch with your custom config and the list of Merge Requests in the "What to Expect" section below will be updated the next time Renovate runs. --- ### What to Expect It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
jimsy commented 2021-01-02 18:49:58 +13:00 (Migrated from gitlab.com)
Copy link

assigned to @jimsy

assigned to @jimsy
jimsy commented 2021-01-04 22:16:47 +13:00 (Migrated from gitlab.com)
Copy link

added 2 commits

Compare with previous version

added 2 commits <ul><li>ccf4635c - 1 commit from branch <code>main</code></li><li>207c07e0 - Add renovate.json</li></ul> [Compare with previous version](/jimsy/gcode/-/merge_requests/1/diffs?diff_id=133863033&start_sha=1bb1a5d0dcdbf7e56cd7ac13de93fe6d54adb61e)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: james/gcode#3
No description provided.
Delete branch "renovate/configure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?