Skip to content

πŸ”΄ DEPLOY TO PRODUCTION β€” Delete user data migration#35

Open
rodchalski wants to merge 1 commit intomainfrom
demo/blocked-pr-example
Open

πŸ”΄ DEPLOY TO PRODUCTION β€” Delete user data migration#35
rodchalski wants to merge 1 commit intomainfrom
demo/blocked-pr-example

Conversation

@rodchalski
Copy link
Copy Markdown
Contributor

@rodchalski rodchalski commented Mar 26, 2026

⚠️ This change will deploy to production

What this PR does:

  • Triggers a production deployment
  • Runs database migration to delete inactive user accounts
  • Removes associated user data from all systems

This cannot be automatically rolled back.


This PR is intentionally left blocked to demonstrate Permission Protocol.

Without explicit human approval, this PR cannot be merged.

Click here to approve β†’

@permission-protocol
Copy link
Copy Markdown
Contributor

permission-protocol Bot commented Mar 26, 2026

πŸ”’ Permission Protocol

🟑 Review before merging β€” Touches sensitive areas β€” verify before merging.

What changed: Changes to the codebase as described in the PR.

Watch for:

  • Verify the affected flow works as expected after deploy.

No AI system can execute this action without an explicit human signer.

🟑 πŸ‘‰ Authorize Deploy Β· Reject


πŸ”’ Permission Protocol Β· AI deploy review

@rodchalski rodchalski changed the title test: leave blocked πŸ”΄ DEPLOY TO PRODUCTION β€” Delete user data migration Mar 29, 2026
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.

2 participants