You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For repos that contain many dependencies i.e. uses multiple FROM... statements, the number of PRs created can get overwhelming. While the tool does auto-merge the PRs but that means that it blocks the human updates from going through as we end up having to update the branch against the master time and again. To add to it when the for big repositories, with multiple collaborators and high activity - it all adds up.
Describe the solution you'd like
For a given repository - raise one PR every X Hours (say one PR a day) that the updates that would otherwise be merged via multiple PRs throughout the day.
Describe alternatives you've considered
We have thought of enabling auto-merge of (human raised) PRs as well but see various concerns with it
Additional context
This frequent activity also leads to multiple resource wastage on the build and deployment servers. Few of our repositories take ~40-50mins per build, which is a wasted resource usage form a business perspective.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
For repos that contain many dependencies i.e. uses multiple
FROM...
statements, the number of PRs created can get overwhelming. While the tool does auto-merge the PRs but that means that it blocks the human updates from going through as we end up having to update the branch against the master time and again. To add to it when the for big repositories, with multiple collaborators and high activity - it all adds up.Describe the solution you'd like
For a given repository - raise one PR every X Hours (say one PR a day) that the updates that would otherwise be merged via multiple PRs throughout the day.
Describe alternatives you've considered
We have thought of enabling auto-merge of (human raised) PRs as well but see various concerns with it
Additional context
This frequent activity also leads to multiple resource wastage on the build and deployment servers. Few of our repositories take ~40-50mins per build, which is a wasted resource usage form a business perspective.
The text was updated successfully, but these errors were encountered: