sequelize-batches icon indicating copy to clipboard operation
sequelize-batches copied to clipboard

Configure Renovate

Open renovate[bot] opened this issue 6 years ago • 2 comments

Mend Renovate

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

  • package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

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

Update dependency sequelize to v6 [SECURITY]
  • Branch name: renovate/npm-sequelize-vulnerability
  • Merge into: master
  • Upgrade sequelize to ^6.0.0
Update dependency sqlite3 to v3.1.13
  • Schedule: ["at any time"]
  • Branch name: renovate/sqlite3-3.x-lockfile
  • Merge into: master
  • Upgrade sqlite3 to 3.1.13
Update dependency babel-preset-env to v1.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/babel-preset-env-1.x-lockfile
  • Merge into: master
  • Upgrade babel-preset-env to 1.7.0
Update dependency flow-bin to ^0.224.0
  • Schedule: ["at any time"]
  • Branch name: renovate/flow-bin-0.x
  • Merge into: master
  • Upgrade flow-bin to ^0.224.0
Update dependency prettier to v1.19.1
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-1.x-lockfile
  • Merge into: master
  • Upgrade prettier to 1.19.1
Update dependency prettier to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x
  • Merge into: master
  • Upgrade prettier to ^3.0.0
Update dependency sqlite3 to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/sqlite3-5.x
  • Merge into: master
  • Upgrade sqlite3 to ^5.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm 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 Mend Renovate. View repository job log here.

renovate[bot] avatar Jun 02 '19 06:06 renovate[bot]

Please make sure to add screenshots or gifs of the change to give a clear picture of the change. If a design PR was made please make sure to link to it along with the JIRA ticket. A Design PR will avoid unnecessary rework that might come up in a PR.

Good Pull Requests adhere to a single responsibility.

  • Break big changes into smaller Pull Requests
  • Big changes increase risk - smaller PRs are easier to review
  • Refactoring changes should be in seperate PRs to avoid noise
  • A story/ticket can have more than 1 PR

Some guidelines on giving and receiving feedback in Code Reviews

  • https://blog.rangle.io/the-art-of-humanizing-pull-requests-prs/
  • https://blog.scottnonnenberg.com/top-ten-pull-request-review-mistakes/
  • https://dev.to/codemouse92/10-principles-of-a-good-code-review-2egA
  • https://dev.to/samjarman/giving-and-receiving-great-code-reviews

ordermentum[bot] avatar Jun 02 '19 06:06 ordermentum[bot]