Skip to content

Replace continuous Dependabot with a bimonthly, approval-gated update - #20

Merged
codemastervy merged 1 commit into
mainfrom
replace-automation
Aug 30, 2026
Merged

codemastervy merged 1 commit into
mainfrom
replace-automation

Conversation

@codemastervy

Copy link
Copy Markdown
Owner

Removes dependabot.yml and the always-on auto-merge workflow. Adds a workflow that checks for updates every 2 months (or on demand via workflow_dispatch), pauses on a GitHub Environment requiring your approval (this is what triggers GitHub's own approval-request email), and only then applies bumps and opens one PR -- which still has to pass CI to merge.

…ated update

Removes dependabot.yml and the auto-merge-on-open workflow entirely --
no more individual dependency PRs appearing and merging on their own.

Adds one workflow that runs itself every 2 months (or on demand): it
checks pip, npm and the Docker base images for anything newer, and if it
finds something, PAUSES on a GitHub Environment ('dependency-approval')
that requires manual review. That pause is what makes GitHub send an
email with a link to an Approve/Reject button -- no third-party mail
service, no credentials, just GitHub's own notification system.

Only after approval does it apply the bumps, open one consolidated PR,
and request auto-merge -- which still can't complete until backend-tests,
frontend-build and docker-build all pass, same as any other PR, enforced
by the branch protection already in place. A dependency check that finds
nothing sends no email at all.
@codemastervy
codemastervy merged commit fbfe38c into main Aug 30, 2026
3 checks passed
@codemastervy
codemastervy deleted the replace-automation branch August 30, 2026 07:57
codemastervy added a commit that referenced this pull request Aug 30, 2026
…ated update (#20)

Removes dependabot.yml and the auto-merge-on-open workflow entirely --
no more individual dependency PRs appearing and merging on their own.

Adds one workflow that runs itself every 2 months (or on demand): it
checks pip, npm and the Docker base images for anything newer, and if it
finds something, PAUSES on a GitHub Environment ('dependency-approval')
that requires manual review. That pause is what makes GitHub send an
email with a link to an Approve/Reject button -- no third-party mail
service, no credentials, just GitHub's own notification system.

Only after approval does it apply the bumps, open one consolidated PR,
and request auto-merge -- which still can't complete until backend-tests,
frontend-build and docker-build all pass, same as any other PR, enforced
by the branch protection already in place. A dependency check that finds
nothing sends no email at all.

Co-authored-by: codemastervy <isherveer@amirulandalib.eu.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant