Skip to content

🩹[Patch]: Configure Dependabot for daily schedule with 7-day cooldown #24

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
MariusStorhaug wants to merge 3 commits into
base: main
Choose a base branch
from
+17 −33
Open

🩹[Patch]: Configure Dependabot for daily schedule with 7-day cooldown #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8f999ec
Configure Dependabot for daily schedule with 7-day cooldown
MariusStorhaug Jan 22, 2026
ad6d520
🩹 [Patch]: Update dependencies for GitHub-Script and Invoke-Pester ac…
MariusStorhaug Jan 22, 2026
c50ca73
🩹 [Patch]: Fix typo in README regarding action output logs
MariusStorhaug Jan 25, 2026
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
4 changes: 3 additions & 1 deletion .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,4 +11,6 @@ updates:
- dependencies
- github-actions
schedule:
interval: weekly
interval: daily
cooldown:
default-days: 7
Comment on lines +15 to +16
Copy link

Copilot AI Jan 25, 2026

Choose a reason for hiding this comment

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

The cooldown configuration option is not a valid Dependabot configuration field according to GitHub's documentation. Dependabot does not support a cooldown mechanism to prevent duplicate PRs within a specified time period. This configuration will likely be ignored or cause validation errors.

If the goal is to reduce PR churn while checking daily, consider using the open-pull-requests-limit option instead to limit the number of concurrent open PRs, or stick with the weekly schedule. The daily schedule will attempt to open PRs for updates as they become available, which may not achieve the desired 7-day cooldown behavior described in the PR description.

Suggested change
cooldown:
default-days: 7
open-pull-requests-limit: 5

Copilot uses AI. Check for mistakes.
18 changes: 0 additions & 18 deletions .github/release.yml
View file
Open in desktop

This file was deleted.

14 changes: 7 additions & 7 deletions .github/workflows/Action-Test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ jobs:
Conclusion: ${{ steps.action-test.conclusion }}
steps:
- name: Checkout repo
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false

Expand All @@ -50,7 +50,7 @@ jobs:
Conclusion: ${{ steps.action-test.conclusion }}
steps:
- name: Checkout repo
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false

Expand All @@ -76,7 +76,7 @@ jobs:
Conclusion: ${{ steps.action-test.conclusion }}
steps:
- name: Checkout repo
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false

Expand All @@ -103,7 +103,7 @@ jobs:
Conclusion: ${{ steps.action-test.conclusion }}
steps:
- name: Checkout repo
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false

Expand All @@ -129,7 +129,7 @@ jobs:
Conclusion: ${{ steps.action-test.conclusion }}
steps:
- name: Checkout repo
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false

Expand Down Expand Up @@ -169,11 +169,11 @@ jobs:
OutputsConclusion: ${{ needs.ActionTestOutputs.outputs.Conclusion }}
steps:
- name: Checkout repo
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false

- name: Aggregated Status
uses: PSModule/Github-Script@v1
uses: PSModule/GitHub-Script@2010983167dc7a41bcd84cb88e698ec18eccb7ca # v1.7.8
with:
Script: tests/Get-AggregatedStatus.ps1
4 changes: 2 additions & 2 deletions .github/workflows/Auto-Release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,11 +26,11 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Checkout Code
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false

- name: Auto-Release
uses: PSModule/Auto-Release@v1
uses: PSModule/Auto-Release@eabd533035e2cb9822160f26f2eda584bd012356 # v1.9.5
with:
IncrementalPrerelease: false
4 changes: 2 additions & 2 deletions .github/workflows/Linter.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,13 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Checkout repo
uses: actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false
fetch-depth: 0

- name: Lint code base
uses: super-linter/super-linter@latest
uses: super-linter/super-linter@d5b0a2ab116623730dd094f15ddc1b6b25bf7b99 # v8.3.2
env:
GITHUB_TOKEN: ${{ github.token }}
VALIDATE_JSON_PRETTIER: false
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ The action provides the following outputs:
To be clear; the action follows the settings file to determine which rules to skip.

4. **View the Results**
The action outputs the results of the tests to goth logs and step summary. If the tests pass, the actions `outcome` will be `success`.
The action outputs the results of the tests to both logs and step summary. If the tests pass, the actions `outcome` will be `success`.
If the tests fail, the actions outcome will be `failure`. To make the workflow continue even if the tests fail, you can set the
`continue-on-error` option to `true`. Use this built-in feature to stop the workflow from failing so that you can aggregate the status of tests
across multiple jobs.
Expand Down
4 changes: 2 additions & 2 deletions action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,7 +248,7 @@ runs:
using: composite
steps:
- name: Get-TestPaths
uses: PSModule/Github-Script@v1
uses: PSModule/GitHub-Script@2010983167dc7a41bcd84cb88e698ec18eccb7ca # v1.7.8
id: paths
env:
PSMODULE_INVOKE_SCRIPTANALYZER_INPUT_Path: ${{ inputs.Path }}
Expand All @@ -262,7 +262,7 @@ runs:
Script: ${{ github.action_path }}/scripts/main.ps1

- name: Invoke-Pester
uses: PSModule/Invoke-Pester@v4
uses: PSModule/Invoke-Pester@882994cbe1ff07c3fc8afdac52404c940f99b331 # v4.2.2
id: test
env:
SettingsFilePath: ${{ fromJson(steps.paths.outputs.result).SettingsFilePath }}
Expand Down
Loading