Repository navigation
Keep production tests and database copy only - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keep only two GitHub Actions workflows: production unit/regression and Worker integration tests, and manual production-to-development database copy. Remove deployment and code-sync automation; development pushes no longer trigger tests. Preserve the required Regression and Worker checks job.
The database action now reports disabled-repository or missing-secret setup errors before installing tools instead of silently skipping. Database automation runs only from main in Telegram-event-management; its environment is branch-restricted and private configuration stays in environment secrets. Existing production read-only export, resource separation, snapshot protections, atomic development import and private-file cleanup remain unchanged.
Validation: actionlint passes; the required production suite runs on this PR. No application changes are promoted.