Renovate configuration presets
- for GitHub
- for GitLab
- go to Renovate Dashboard to add your project,
- accept Renovate Bot PR
- ✅ Automerge only when safe
- When dev dependency that is self validated by CI
- When project is following semantic-versioning and well maintained
- 🚄 Focus on productivity
- The configuration should not overburden the team by creating a great amount of PR, it should be a safe way to automate and save time
- ✓ Main Supported Technologies
- NodeJS
- Docker
- React Native & Ionic (no upgrade for native dependencies)
- 🗓️ Scheduled to run outside working hours (night and weekend)
For an application repository, the recommended strategy is to pin every dependencies, use this configuration:
{
"extends": ["github>Inthememory/renovate-config:application"]
}For a library repository (only dev dependencies will be pinned), use this configuration:
{
"extends": ["github>Inthememory/renovate-config:library"]
}For an unmaintained or untested repository include the configuration (will disable automerge and limit maximum PR). Add a safe guard that avoids too many pull request and disables auto merge.
{
"extends": [
// ...
"github>Inthememory/renovate-config:safeLegacy"
]
}Later, when the PR amount is lower and the application you should remove to safeLegacy.json
Renovate will create many pull request. If something fails or a human action is required, there must be an owner to avoid a stock of waiting pull requests
Assign a person
{
// ...
"assigneeSampleSize": 2, // Number of person to pick
"assignees": ["john_doe"] // the github username
}Assign a team
{
// ...
"assigneeSampleSize": 2, // Number of person to pick
"assignees": ["team:maintainers"] // 'team:' + the github team slug
}Read the documentation to improve your configuration.
UNLICENSED © VusionIntelligence