chore: deprecate /api/git endpoint used by legacy git-integration (CM-767) #3567
+2
−151
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
themarolt
approved these changes
Nov 5, 2025
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.
This pull request removes the legacy Git integration API endpoint and updates documentation to reflect the new Git Integration V2 architecture. The main focus is deprecating outdated code and clarifying the integration's current design and workflow.
Deprecation of legacy Git integration:
gitGetRemotesAPI handler (gitGetRemotes.ts), which previously supported fetching legacy Git integration remotes./gitGET route from the integration API registration (index.ts).Documentation updates for Git Integration V2:
README.mdcontent with a summary of the new Kubernetes-based Git Integration V2, describing its workflow and architecture.