Steve Hipwell

This commit introduces a **new `ClientID` field** to the `App` struct within the **GitHub integration module**, enabling the system to store the unique client identifier for GitHub Applications. This **enhances the `App` model** by providing a dedicated attribute for this crucial piece of information, which is essential for various authentication and API interaction scenarios. A corresponding `GetClientID` accessor method has been added to safely retrieve this new field, along with a dedicated test case to ensure its correct functionality. This **new feature** lays the groundwork for future capabilities that depend on identifying GitHub Apps by their client ID.

This commit delivers a **bug fix** for **GitHub organization custom properties**, specifically addressing an issue with multi-select property default values. Previously, the `DefaultValueStrings` function in `github/orgs_properties.go` did not correctly handle default values when they were of type `[]any`, leading to potential data type mismatches. The update ensures proper processing of these values, and new test cases have been added to `github/orgs_properties_test.go` to validate the fix and enhance coverage for multi-select custom properties. This change guarantees that custom property default values are consistently and correctly applied, improving the reliability of organization settings.

This commit **refactors** the Go module caching within the **CI/CD test workflow** by updating the `.github/workflows/tests.yml` configuration. It specifically leverages the built-in `cache-dependency-path` feature of the `setup-go` action to manage Go module dependencies. This **chore** improves the efficiency and reliability of caching during test runs, streamlining the CI process. The change ensures more consistent and potentially faster execution of tests by utilizing a more robust and integrated caching strategy.

This commit **enhances the handling of custom property defaults** within the **GitHub integration**, specifically for **organization custom properties**. It **introduces a breaking change** by making `CustomProperty.DefaultValue` type `any` and `CustomProperty.ValueType` type `PropertyValueType` to support more flexible default values. To manage this, the change **adds type-safe accessor methods** such as `DefaultValueString`, `DefaultValueStrings`, and `DefaultValueBool` to `github/orgs_properties.go`. This **refactoring** improves the robustness and flexibility of **custom property management** by providing explicit type handling for default values, requiring updates to existing code that directly accesses `DefaultValue`.

This commit provides a **bug fix** for the **GitHub integration**, specifically addressing how **pull request rule parameters** are handled during JSON serialization. It modifies the `PullRequestRuleParameters` struct in `github/rules.go` to ensure the `AllowedMergeMethods` field is **omitted from JSON output if it is empty or unset**. This change prevents potential issues when processing or storing GitHub rules where merge method restrictions are not explicitly defined, improving the robustness of **rule configuration and application**.

This commit introduces a **new feature** by adding a **'repository' target to the GitHub ruleset integration**, allowing for the definition of rules that apply directly to repositories. It significantly updates the `github` package, specifically `github/rules.go`, to define new repository-specific rule types and adjust JSON marshaling/unmarshaling to support them. New accessor methods like `GetRepositoryCreate` and `GetRepositoryVisibility` are added in `github/github-accessors.go` to retrieve parameters for these new repository-level rules. This enhancement provides more granular control over repository actions such as creation, deletion, transfer, and visibility within the ruleset system.

This commit primarily performs a **maintenance update** by upgrading the project's **`golangci-lint` tool to version v2.7.0**, ensuring the use of the latest static analysis features. This involves updating the version specified in `.custom-gcl.yml` and `script/lint.sh`, and adding `custom-gcl.exe` to `.gitignore` to support Windows environments. Concurrently, a **refactoring** is applied to the `tools/gen-release-notes` utility, specifically modernizing string manipulation in `stripPRHTML` and `getTagSequence` using `strings.Cut`. This dual-purpose commit enhances the **CI/CD linting process** and improves the internal code quality of the **release notes generation tool**.

This commit **introduces new API operations** by updating the `openapi_operations.yaml` specification, marking a significant **feature enhancement**. It expands the API surface to include functionalities across various domains such as **enterprise actions, app installations, billing, organization actions, dependabot, attestations, repository actions, issue dependencies, and user attestations**. This update provides developers with a broader set of tools to interact programmatically with these subsystems, ensuring the API documentation accurately reflects the latest available capabilities. The commit also synchronizes the OpenAPI commit hash, reflecting the most current upstream specification.

This commit **fixes** a potential type mismatch by **changing the `AppID` field** within the **`github/checks` package** from `int` to `int64`. This **breaking change** primarily affects the `ListCheckSuiteOptions` struct and the `GetAppID` accessor method, which now consistently return `int64`. The update ensures proper handling of application identifiers, aligning the client library with the underlying GitHub API's expected data types and preventing potential overflow issues. Consequently, consumers of these types and methods will need to adjust their code to use `int64` for application IDs.

This commit introduces a **new capability** to the **GitHub client library**, allowing users to **disable the client's internal rate limit checking mechanism**. A new `DisableRateLimitCheck` field has been added to the `Client` struct, which, when enabled, causes the `bareDo` method to conditionally skip all rate limit checks and updates. This provides greater control for users who manage rate limiting externally or interact with GitHub Enterprise instances, and is supported by new unit tests. The **documentation** in `README.md` has been updated to explain this new option and its interaction with other rate limit bypass features.

This commit provides a **maintenance fix** to the **CI/CD pipeline** by updating the **GitHub Actions workflow** in `.github/workflows/tests.yml`. It specifically enables OIDC authentication and grants the required permissions for **Codecov uploads**. This resolves previous issues with code coverage reporting, ensuring that accurate test coverage metrics are consistently available for the project.

This commit **introduces a new `REVIEWERS` file** to the project, which lists GitHub usernames of individuals available for pull request reviews. Concurrently, the **contributor guidelines** in `CONTRIBUTING.md` are updated to explain this new review process and how to utilize the `REVIEWERS` file. This **maintenance chore** enhances project governance and aims to streamline the pull request review workflow by providing clear guidance on who to involve. The change improves the contributor experience by making the review process more transparent and efficient.

This commit **introduces a new `NotificationSetting` field to the `Team` struct** within the **`github` module**, enhancing the data model to support team-level notification preferences. It adds a corresponding accessor method, `GetNotificationSetting`, to allow retrieval of this new property. This **new capability** primarily affects the **GitHub API client library**, enabling applications to store and manage notification settings for teams. The change includes necessary **test updates** across `copilot_test.go`, `github-accessors_test.go`, and `github-stringify_test.go` to ensure the new field and its accessor function correctly.

This commit introduces **comprehensive support for GitHub Enterprise rulesets**, enabling their creation, retrieval, update, and deletion within the **`github` module**. It also **enhances existing organization and repository ruleset management** by adding new functions to clear bypass actors and introducing new types for merge methods and organization conditions, alongside new accessor methods like `GetOrganizationID` for ruleset conditions. A **breaking change** is included, as `Create*Ruleset` and `Update*Ruleset` functions across all ruleset types now pass the `ruleset` parameter by value instead of by reference, requiring consumers to adapt. This **new capability** significantly expands the project's ability to manage GitHub rulesets at the enterprise level and refines existing ruleset APIs.