I was working on to setup renovatebot though self-hosted and I saw they have config:recommended where it had "group:monorepos". Why do we want to group monorepos separately when compared with other dependencies?
1
There are 1 best solutions below
Related Questions in RENOVATE
- Installing nodejs with node-gyp without internet
- Basic Renovate Configuration for Angular Project
- Why renovatebot separate monorepo
- Renovate Error: "Each packageRule must contain at least one match* or exclude* selector" when configuring a custom Maven repository
- How to get renovate to update the java version in my pom.xml
- Renovate prevent query for local dependencies in maven
- Use renovate to update git submodule branch and commit
- Renovate minimumReleaseAge and internalChecksFilter="strict" does not work with group:allNonMajor PR for noise reduction
- Renovate Bot Schedule configuration for biweekly renovate PRs is not working
- Configuring Dependabot/Renovate: Seeking Assistance with Specific Settings
- How to run/test renovate bot locally?
- How to configure Renovate to watch latest commits from branch
- How to update only dev dependencies in Renovate for Composer?
- Why PNPM marks my package with "version: link:" after "pnpm install ..." command?
- Renovate: update dependency with syntactically different semver tags
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
group:monoreposis a preset that enables grouping in dependencies part of well known monorepos.If you use two dependencies A and B, both have an upgrade available and they are actually originating from the same Git monorepo, you likely want to update both together in the same PR/commit. That's the purpose of this preset.
Otherwise, you'd get two PRs: one for A and for B.
Why do you want that? Because there are chances that you need to upgrade both A and B at the same time for them to work properly. Or at the very least for consistency, even if they'd work separately: why would you upgrade only one?