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 #75

Closed
wants to merge 1 commit into from
Closed

Configure Renovate #75

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 9, 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
  • Update existing lock files only when package.json is modified
  • 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.


You have configured Renovate to use branch master as base branch.

What to Expect

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

Update github.com/saracen/walker commit hash to 324a081
  • Schedule: "at any time"
  • Branch name: renovate/github.com-saracen-walker-digest
  • Merge into: master
  • Upgrade github.com/saracen/walker to 324a081bae7e580aa0bf3afe8164acb16634afca
Update golang.org/x/net commit hash to c0dbc17
  • Schedule: "at any time"
  • Branch name: renovate/golang.org-x-net-digest
  • Merge into: master
  • Upgrade golang.org/x/net to c0dbc17a35534bf2e581d7a942408dc936316da4
Update module mattn/go-isatty to v0.0.11
  • Schedule: "at any time"
  • Branch name: renovate/github.com-mattn-go-isatty-0.x
  • Merge into: master
  • Upgrade github.com/mattn/go-isatty to v0.0.11

🚸 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.


Newsflash: Renovate has joined WhiteSource, and is now free for all use. Learn more or view updated terms and privacy policies.

@mattn
Copy link
Owner

mattn commented Jan 9, 2020

I don't want to renovate for this.

@mattn mattn closed this Jan 9, 2020
@mattn mattn deleted the renovate/configure branch January 9, 2020 10:26
@renovate
Copy link
Author

renovate bot commented Jan 9, 2020

Renovate is disabled

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.

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.

2 participants