chore: preserve current staging source on main - #38
Merged
SourceSenseiTheRealOne merged 1 commit intoSep 8, 2026
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Owner
Author
|
Bounded promotion review at 5f5cc7c: candidate tree fb203ec04715b817daf98f39a474b66f3f2e5f53 exactly matches verified staging; no product-source changes were introduced by promotion. Exact-head GitHub checks passed. This is a preservation/tree review, not a new independent security audit. |
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
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.
Pre-reset promotion. Source:
b7244010ff5a58690dbc191bc712d210231f5dd0. Exact source tree:fb203ec04715b817daf98f39a474b66f3f2e5f53. Target-based commit retains existing target history and avoids squash-history conflicts. Source content is unchanged; credentials remain in the private D: backup. No deployment workflow is manually dispatched.