This PR improves code clarity by renaming misleading variable names in API parameter hashtables throughout the codebase.

• Fixes 🩹 [Patch]: Rename $inputObject variables to $apiParams in API calls #433

Problem

Previously, the variable $inputObject was used to represent hashtables containing parameters for API requests. However, $inputObject typically implies pipeline input rather than API request parameters, making it confusing and misleading for developers maintaining the code.

Example of confusing usage:

$inputObject = @{
    Method      = 'DELETE'
    APIEndpoint = "/orgs/$Name"
    Context     = $Context
}

Invoke-GitHubAPI @inputObject

Solution

Renamed all occurrences of $inputObject used specifically for API request parameter hashtables to $apiParams for clarity and better readability.

After the change:

$apiParams = @{
    Method      = 'DELETE'
    APIEndpoint = "/orgs/$Name"
    Context     = $Context
}

Invoke-GitHubAPI @apiParams

Changes Made

• Files Modified: 211 files total
• REST API calls: 202 files with Invoke-GitHubAPI @inputObject → Invoke-GitHubAPI @apiParams
• GraphQL calls: 9 files with Invoke-GitHubGraphQLQuery @inputObject → Invoke-GitHubGraphQLQuery @apiParams
• Lines Changed: 595 insertions, 595 deletions (pure variable renaming)

Scope

✅ Changed: All occurrences where $inputObject explicitly represents parameters passed to Invoke-GitHubAPI or Invoke-GitHubGraphQLQuery

✅ Preserved: Parameters named $InputObject intended for pipeline input objects (such as [Parameter(ValueFromPipeline)])

Validation

• All PowerShell syntax validation passes
• Pipeline parameters correctly preserved (e.g., [GitHubVariable[]] $InputObject in Remove-GitHubVariable)
• Zero remaining $inputObject variables used with API calls
• No functional changes - pure variable renaming

Outcome

Improved code clarity and maintainability, reducing potential confusion for future development and maintenance by clearly distinguishing API parameter hashtables from pipeline input parameters.