Skip to content

Create dependabot.yml configuration for develop and release/3.2 branches #173

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.

Sign up for GitHub

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

Open
vsethi09 wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Create dependabot.yml configuration for develop and release/3.2 branches #173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

version: 2
updates:
- package-ecosystem: "gomod" # See documentation for possible values

Check warning on line 8 in .github/dependabot.yml

View workflow job for this annotation

GitHub Actions / zizmor-output

dependabot-cooldown 

dependabot.yml:8: insufficient cooldown in Dependabot updates: missing cooldown configuration
directory: "/" # Location of package manifests
schedule:
interval: "daily"
Comment on lines +10 to +11

@gemini-code-assist gemini-code-assist Bot Aug 20, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Running Dependabot updates daily for Go modules can create a high volume of pull requests, leading to review fatigue and unnecessary CI/CD load. Changing the interval to weekly is generally recommended for Go projects to keep updates manageable.

    schedule:
      interval: "weekly"

@deepika-lalwani123 deepika-lalwani123 Aug 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

target-branch: develop
- package-ecosystem: "gomod" # See documentation for possible values

Check warning on line 13 in .github/dependabot.yml

View workflow job for this annotation

GitHub Actions / zizmor-output

dependabot-cooldown 

dependabot.yml:13: insufficient cooldown in Dependabot updates: missing cooldown configuration
directory: "/" # Location of package manifests
schedule:
interval: "daily"
Comment on lines +15 to +16

@gemini-code-assist gemini-code-assist Bot Aug 20, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Running Dependabot updates daily for Go modules can create a high volume of pull requests, leading to review fatigue and unnecessary CI/CD load. Changing the interval to weekly is generally recommended for Go projects to keep updates manageable.

    schedule:
      interval: "weekly"

@deepika-lalwani123 deepika-lalwani123 Aug 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

target-branch: release/3.2
Loading