Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the interval schedule in dependabot.yml configurable #217

Closed
hkadakia opened this issue Sep 6, 2024 · 1 comment · Fixed by #222
Closed

Make the interval schedule in dependabot.yml configurable #217

hkadakia opened this issue Sep 6, 2024 · 1 comment · Fixed by #222
Labels
enhancement New feature or request

Comments

@hkadakia
Copy link
Contributor

hkadakia commented Sep 6, 2024

Is your feature request related to a problem?

Currently when a new dependabot.yml file is created it defaults to run weekly. There could be a need for users to run it more frequently. Having a way to specify that as part of environment variable could be helpful. The default can remain as weekly if not specified.

Describe the solution you'd like

Introduce a new environment variable for making the schedule configurable. This would give flexibility to the user to select the frequency at which dependabot should look for new packages and dependencies.

Describe alternatives you've considered

Merge the pull request created by dependabot and then create a new pull request to modify the schedule to the frequency user wants. This is a current workaround but having a way users can specify that at org level can help them additional step to create new pull request across multiple repos in their orgs.

Additional context

No response

@hkadakia hkadakia added the enhancement New feature or request label Sep 6, 2024
jmeridth added a commit to jmeridth/evergreen that referenced this issue Sep 12, 2024
…ironment variables

Closes github#217

- [x] new environment variables: SCHEDULE, SCHEDULE_DAY
- [x] update README with new environment variable information
- [x] passing specs

Signed-off-by: jmeridth <jmeridth@gmail.com>
jmeridth added a commit to jmeridth/evergreen that referenced this issue Sep 12, 2024
…ironment variables

Closes github#217

- [x] new environment variables: SCHEDULE, SCHEDULE_DAY
- [x] update README with new environment variable information
- [x] passing specs

Signed-off-by: jmeridth <jmeridth@gmail.com>
jmeridth added a commit to jmeridth/evergreen that referenced this issue Sep 12, 2024
…ironment variables

Closes github#217

- [x] new environment variables: SCHEDULE, SCHEDULE_DAY
- [x] update README with new environment variable information
- [x] passing specs

Signed-off-by: jmeridth <jmeridth@gmail.com>
jmeridth added a commit to jmeridth/evergreen that referenced this issue Sep 12, 2024
…ironment variables

Closes github#217

- [x] new environment variables: SCHEDULE, SCHEDULE_DAY
- [x] update README with new environment variable information
- [x] passing specs

Signed-off-by: jmeridth <jmeridth@gmail.com>
jmeridth added a commit to jmeridth/evergreen that referenced this issue Sep 12, 2024
…ironment variables

Closes github#217

- [x] new environment variables: SCHEDULE, SCHEDULE_DAY
- [x] update README with new environment variable information
- [x] passing specs

Signed-off-by: jmeridth <jmeridth@gmail.com>
jmeridth added a commit to jmeridth/evergreen that referenced this issue Sep 12, 2024
…ironment variables

Closes github#217

- [x] new environment variables: SCHEDULE, SCHEDULE_DAY
- [x] update README with new environment variable information
- [x] passing specs

Signed-off-by: jmeridth <jmeridth@gmail.com>
@hkadakia
Copy link
Contributor Author

With this change, is it possible to specify different schedule for different ecosystem. For eg. I would like security patches to be run weekly but any non-security issues can be run monthly? Do you want me to create a new issue for this request if at all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant