Skip to content

Conversation

@SBALAVIGNESH123
Copy link

@SBALAVIGNESH123 SBALAVIGNESH123 commented Feb 10, 2026

I’ve merged the latest changes from v4.x into the branch, ensuring that our pgBackRest implementation remains intact. The merge conflicts in StandalonePostgresql.php were handled manually to preserve the new backup logic while pulling in the upstream model updates, and I accepted the incoming changes for all other unrelated files to keep things clean. I also took the time to address the GitGuardian alert by sanitizing the test credentials and did a quick polish pass on PgBackrestService.php
to remove some verbose comments, so the code looks much more professional now. Everything builds and passes local checks, so it’s ready for review

@gitguardian
Copy link

gitguardian bot commented Feb 10, 2026

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

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