Skip to content

fix: fixing force push for gitops #5152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 3, 2024
Merged

fix: fixing force push for gitops #5152

merged 4 commits into from
Jun 3, 2024

Conversation

subhashish-devtron
Copy link
Contributor

@subhashish-devtron subhashish-devtron commented May 22, 2024

Description

Fixes #5225

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I have added all the required unit/api test cases.
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.

Does this PR introduce a user-facing change?


nishant-d
nishant-d previously approved these changes May 22, 2024
Copy link

sonarqubecloud bot commented Jun 3, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@subhashish-devtron subhashish-devtron merged commit 4cf44b2 into main Jun 3, 2024
@subhashish-devtron subhashish-devtron deleted the gitops-push-fix branch June 3, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: Gitops force push can possibly have side-effects
2 participants