Separate schedule
per dependencies
#15562
Unanswered
radeksimko
asked this question in
Code Security
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
All use cases / examples shown in the docs involving
allow
orignore
would suggest that it is not possible to have multiple schedules for the same combination of ecosystem/directory/branch.This is also clear from the error message when I tried submitting the following config.
I do understand if the motivation behind this limitation was to prevent multiple jobs for the same ecosystem which all do the same thing, created by accident, but I think the limitation goes a bit too far in limiting some valid use cases.
I do think
schedule
should be considered as another key in the "unique set" (alongside 'package-ecosystem', 'directory', and 'target-branch'). In NPM ecosystem in particular, there are often dev dependencies such as@types/*
which create a lot of noise due to frequent updates. Generally dev dependencies typically only affect the dev environment and so we'd like to treat them differently from the production ones and set e.g. weekly schedule for them.Is there a reason this is not possible today?
Beta Was this translation helpful? Give feedback.
All reactions