Skip to content

Common Dependabot #15

@MSevey

Description

@MSevey

Look into creating a common dependabot file in this repo and then using github actions to push the file out to all the other repos.

Something similar to this thread: https://devops.stackexchange.com/questions/17893/best-practices-for-managing-github-actions-workflows-in-an-organization

Example workflow might look like:

  • if dependabot file has changed, add label to PR
  • on merge, check for the diff or label to trigger sending out updates
  • copy the file into the repos via PR

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions