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

Configure Renovate - autoclosed #3

Merged
merged 1 commit into from Aug 19, 2020
Merged

Configure Renovate - autoclosed #3

merged 1 commit into from Aug 19, 2020

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 19, 2020

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

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


Detected Package Files

  • go.mod (gomod)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs 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 PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

🔡 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 Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

chore(deps): update module gookit/color to v1.2.7
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-gookit-color-1.x
  • Merge into: master
  • Upgrade github.com/gookit/color to v1.2.7
chore(deps): update module gookit/color to v1.2.7
  • Schedule: ["at any time"]
  • Branch name: renovate/gopkg.in-gookit-color.v1-1.x
  • Merge into: master
  • Upgrade gopkg.in/gookit/color.v1 to v1.2.7
chore(deps): update module kr/pretty to v0.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-kr-pretty-0.x
  • Merge into: master
  • Upgrade github.com/kr/pretty to v0.2.1

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.


❓ 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 PR has been generated by WhiteSource Renovate. View repository job log here.

@github-actions
Copy link

Pull Request Test Coverage Report for Build 79736cb69d40d15a08b2402851cd2b14dad28837-PR-3

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build a3c65762d46dbc61fd11f3c2616d023038f9c7a8: 0.0%
Covered Lines: 116
Relevant Lines: 116

💛 - Coveralls

@clok clok merged commit 103a071 into master Aug 19, 2020
@clok clok deleted the renovate/configure branch August 19, 2020 22:01
@renovate renovate bot changed the title Configure Renovate Configure Renovate - autoclosed Aug 19, 2020
Sign up for free to 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.

None yet

2 participants