fix: optimizations in git flows

[subhashish-devtron]

#Fixes 88

[gitguardian]

⚠️ GitGuardian has uncovered 11 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9190503	Triggered	Username Password	cbd5a5d	pkg/git/RepositoryManagerIT_test.go	View secret
9190503	Triggered	Username Password	51743fc	pkg/git/RepositoryManagerIT_test.go	View secret
9190503	Triggered	Username Password	ab22c47	pkg/git/RepositoryManagerIT_test.go	View secret
9190503	Triggered	Username Password	e8a34c6	pkg/git/RepositoryManagerIT_test.go	View secret
6669478	Triggered	PGP Private Key	9ffc8e7	vendor/github.com/ProtonMail/go-crypto/openpgp/keys_test_data.go	View secret
6669479	Triggered	PGP Private Key	9ffc8e7	vendor/github.com/ProtonMail/go-crypto/openpgp/keys_test_data.go	View secret
6669480	Triggered	PGP Private Key	9ffc8e7	vendor/github.com/ProtonMail/go-crypto/openpgp/keys_test_data.go	View secret
6669481	Triggered	PGP Private Key	9ffc8e7	vendor/github.com/ProtonMail/go-crypto/openpgp/keys_test_data.go	View secret
6669482	Triggered	PGP Private Key	9ffc8e7	vendor/github.com/ProtonMail/go-crypto/openpgp/keys_test_data.go	View secret
6669483	Triggered	PGP Private Key	9ffc8e7	vendor/github.com/ProtonMail/go-crypto/openpgp/keys_test_data.go	View secret
6669484	Triggered	PGP Private Key	9ffc8e7	vendor/github.com/ProtonMail/go-crypto/openpgp/keys_test_data.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>