-
Notifications
You must be signed in to change notification settings - Fork 5
refactor: eliminate duplication and fix regressions #16
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
Closed
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
06fb8df
ci: optimize workflow to reduce redundancy and refine permissions
71d3ac0
ci: fix syntax errors in workflow file
bf9850c
docs: resolve SonarCloud issues and refactor for complexity
08fd2b5
refactor: extract BaseGitService to reduce duplication and fix lint/t…
6c0ca4c
fix: resolve TS build errors due to unchecked indexed access
26be2e8
refactor: address gemini-code-assist bot reviews
d44495e
refactor: eliminate duplication by moving encoding logic to BaseGitSe…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a batch push operation, performing two extra
getFilecalls per file (one before to get the SHA and one after to update metadata) is inefficient and doubles the network overhead.existingShais often already known from the preceding conflict check or local metadata.pushFileAPI response from GitHub (and commit info from GitLab) can be used to update metadata without an additional fetch. Consider updating thepushFileinterface to return the new SHA.