Repository navigation
ci: add dependabot coverage for actions and pip - #4
Merged
Merged
Conversation
Adds a weekly grouped `github-actions` entry (plus `pip`) so action and dependency updates arrive as reviewable pull requests. The workflows themselves are upstream-owned and are left untouched: this fork's convention is to keep fork-local changes additive so `upstream/main` merges stay clean and to take upstream's step-level workflow changes on top.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
.github/dependabot.ymlwith weekly, groupedgithub-actionsandpipupdates.This pull request deliberately contains no workflow pin changes. This repository is the tracked fork of
infer-actively/pymdp, whoseAGENTS.mdrequires fork-local changes to stay additive so that merges fromupstream/mainstay clean, and states that upstream's step-level workflow changes are taken on top. Everyuses:line in the workflows is upstream-owned, so pinning them here would create line-level conflicts on every upstream sync; that coverage belongs upstream instead.A new Dependabot configuration file cannot conflict with an upstream sync, so it is the one part of the CI-hygiene sweep that can land in the fork safely.