#!/bin/bash
# Description: Check if other request files follow the same pattern
# Expected: All Git-related request files should use AxiosPromise

# Search for request files that might not be using AxiosPromise
rg -t typescript "Promise<AxiosResponse" "app/client/src/git/requests"

# Verify the consistent usage of AxiosPromise
rg -t typescript "AxiosPromise" "app/client/src/git/requests"

#!/bin/bash
# Search for request files that might not be using AxiosPromise
rg "Promise<AxiosResponse" app/client/src/git/requests/

# Verify the consistent usage of AxiosPromise
rg "AxiosPromise" app/client/src/git/requests/

# List all files in the git requests directory to ensure we're searching in the right place
fd . app/client/src/git/requests/

#!/bin/bash
# Description: Check for inconsistent return type patterns in API request files
# Expected: All files should use AxiosPromise instead of Promise<AxiosResponse>

# Search for files that might still use the old pattern
rg -l "Promise<AxiosResponse" "app/client/src/git/requests/"

# Search for files using the new pattern for comparison
rg -l "AxiosPromise" "app/client/src/git/requests/"

#!/bin/bash
# Let's examine the actual return type declarations in these files
rg "export default (async )?function.*:.*Promise|AxiosPromise" app/client/src/git/requests/ -A 1

#!/bin/bash
# Description: Check if other request files use AxiosPromise consistently
# Expected: Similar return type pattern in other request files

rg -t typescript "Promise<AxiosResponse<|AxiosPromise<" "app/client/src/git/requests/"

#!/bin/bash
# Let's try with proper file extension and without typescript flag
rg "Promise<AxiosResponse<|AxiosPromise<" app/client/src/git/requests/

# Also search for all files in the directory to ensure we're looking at the right place
ls -la app/client/src/git/requests/

#!/bin/bash
# Description: Check for consistent usage of AxiosPromise across request files
# Expected: All git request files should use AxiosPromise instead of Promise<AxiosResponse>

# Search for any remaining Promise<AxiosResponse> in git request files
rg -l "Promise<AxiosResponse" "app/client/src/git/requests/"

# Search for consistent AxiosPromise usage
rg -l "AxiosPromise" "app/client/src/git/requests/"

#!/bin/bash
# Check actual return type declarations in request files
rg "Promise<AxiosResponse" "app/client/src/git/requests/" -A 1
rg "AxiosPromise" "app/client/src/git/requests/" -A 1

#!/bin/bash
# Search for any remaining Promise<AxiosResponse> types that could be simplified
rg -l "Promise<AxiosResponse" app/client/src/git/requests/

#!/bin/bash
# Let's check for both AxiosPromise and Promise<AxiosResponse> patterns in git requests
rg -g "*.ts" "AxiosPromise|Promise<AxiosResponse" app/client/src/git/requests/ -A 1

# Also check the imports of axios types
rg -g "*.ts" "import.*axios" app/client/src/git/requests/

#!/bin/bash
# Description: Check if other Git request files use Promise<AxiosResponse> that could be simplified to AxiosPromise

# Search for Promise<AxiosResponse> in Git request files
rg -t typescript "Promise<AxiosResponse" "app/client/src/git/requests/"

# Search for AxiosPromise usage for comparison
rg -t typescript "AxiosPromise" "app/client/src/git/requests/"

#!/bin/bash
# Search for Promise<AxiosResponse> in Git request files without file type filter
rg "Promise<AxiosResponse" "app/client/src/git/requests/"

# Search for AxiosPromise usage for comparison
rg "AxiosPromise" "app/client/src/git/requests/"

#!/bin/bash
# Description: Check if other request files use the same return type pattern

# Search for files with similar patterns
rg -l "Promise<AxiosResponse<" "app/client/src/git/requests/"

# Check the actual return types in request files
ast-grep --pattern 'export $_ function $_($_): Promise<AxiosResponse<$_>>' "app/client/src/git/requests/"

#!/bin/bash
# Let's try a different approach to check return types in request files

# First, let's see what files exist in the requests directory
fd . "app/client/src/git/requests/"

# Then check for both patterns (AxiosPromise and Promise<AxiosResponse)
rg "AxiosPromise|Promise<AxiosResponse" "app/client/src/git/requests/" -A 1

# Also check for function return type declarations
ast-grep --pattern 'function $_($_): $_ {' "app/client/src/git/requests/"

#!/bin/bash
# Description: Check return types in other Git request files
# Expected: Should find similar AxiosPromise usage pattern

rg -t typescript "AxiosPromise<.*Response>" "app/client/src/git/requests/"

#!/bin/bash
# Let's try with a more reliable approach to find TypeScript files and check return types
# First, let's find all TypeScript files in the git requests directory
fd ".*\.ts$" "app/client/src/git/requests/" --exec rg -l "AxiosPromise|Promise<AxiosResponse"

# Then let's check the actual return type patterns in these files
fd ".*\.ts$" "app/client/src/git/requests/" --exec rg -A 1 "): (AxiosPromise|Promise<AxiosResponse)" {}

#!/bin/bash
# Let's check the content of a few git request files to see the return type patterns
for file in app/client/src/git/requests/{importGitRequest,pullRequest,mergeRequest}.ts; do
    echo "=== $file ==="
    rg "Promise|AxiosPromise" "$file" -A 1
done

#!/bin/bash
# Description: Check for consistent usage of checkoutBranchRequest
# Look for any potential direct AxiosResponse type usage that could be simplified

# Search for checkoutBranchRequest usage
rg -A 3 "checkoutBranchRequest\(" 

# Search for potential AxiosResponse types that could be simplified
ast-grep --pattern 'Promise<AxiosResponse<$_>>'

#!/bin/bash
# Search for files importing checkoutBranchRequest
rg -l "import.*checkoutBranchRequest"

# Search for CheckoutBranchResponse type usage
rg "CheckoutBranchResponse"

# Look for similar checkout branch related functions
rg -A 3 "checkout.*Branch"

# Check the type definition
fd "CheckoutBranchResponse.ts|CheckoutBranchRequestParams.ts" --exec cat {}

#!/bin/bash
# Search for the type definitions
rg -A 5 "interface CheckoutBranchRequestParams|type CheckoutBranchResponse"

# Check the usage in saga
rg -A 10 "function\* checkoutBranchSaga"

# Check if there are any direct usages of the API response type
rg "AxiosResponse<CheckoutBranchResponse>"

#!/bin/bash
# Search for GitContextValue usage to ensure compatibility
rg "GitContextValue" --type ts -A 2

#!/bin/bash
# Search for UseGitMetadataReturnValue and UseGitConnectReturnValue usage
rg "UseGitMetadataReturnValue|UseGitConnectReturnValue" --type ts -A 2

# Find the interface definitions
ast-grep --pattern 'interface UseGitMetadataReturnValue {
  $$$
}'

ast-grep --pattern 'interface UseGitConnectReturnValue {
  $$$
}'

#!/bin/bash
# Search for return type definitions to check for property conflicts
ast-grep --pattern 'interface Use$_ReturnValue {
  $$$
}'

#!/bin/bash
# Let's try a different approach to find the return types by looking for the hook definitions
ast-grep --pattern 'const use$_ = (): $_ => {'

# Also search for type definitions that might be in separate files
rg "type Use.*ReturnValue" --type ts

# And check the actual hook implementations
rg "export const use.*ReturnValue" --type ts -A 5

#!/bin/bash
# Let's look for the hook implementations directly
rg "useGit.*ReturnValue" --type ts -A 2

# Also search for the individual hooks
rg "const useGit(Metadata|Ops|Branches|Connect|Settings)" --type ts -A 5

# Check the actual spread usage context
rg "\.\.\.useGit.*ReturnValue" --type ts -A 5

#!/bin/bash
# Let's examine the individual hook implementations to see their return values
rg "const useGitMetadata" -A 20 --type ts
rg "const useGitOps" -A 20 --type ts
rg "const useGitBranches" -A 20 --type ts
rg "const useGitSettings" -A 20 --type ts

# Also look for any type definitions for these hooks
rg "type GitMetadata|type GitOps|type GitBranches|type GitSettings" --type ts

#!/bin/bash
# Let's check the GitMetadata type definition and look for the hook implementations
rg "export type GitMetadata" -A 10 --type ts

# Look for the actual hook implementations in their respective files
fd "useGitMetadata.ts|useGitOps.ts|useGitBranches.ts|useGitSettings.ts|useGitConnect.ts" --type f --exec cat {}

#!/bin/bash
# Search for similar error handling patterns in other saga files
rg -A 2 "catch \(error\)" "app/client/src/git/sagas/"

#!/bin/bash
# Check the complete error handling implementation in sagas
rg -A 5 "catch \(error\)" "app/client/src/git/sagas/triggerAutocommitSaga.ts"

# Check error action types
ast-grep --pattern 'gitArtifactActions.$_Error'

#!/bin/bash
# Search for error action types in git artifact actions
rg "gitArtifactActions\.\w+Error" "app/client/src/git/sagas/"

# Check the error handling implementation in other sagas
rg -A 3 "gitArtifactActions\.\w+Error" "app/client/src/git/sagas/"