Skip to content

feat: Expose default_repository_branch and secret_scanning_validity_checks_enabled#3391

Open
JamBalaya56562 wants to merge 1 commit intointegrations:mainfrom
JamBalaya56562:feat/expose-default-branch-and-validity-checks
Open

feat: Expose default_repository_branch and secret_scanning_validity_checks_enabled#3391
JamBalaya56562 wants to merge 1 commit intointegrations:mainfrom
JamBalaya56562:feat/expose-default-branch-and-validity-checks

Conversation

@JamBalaya56562
Copy link
Copy Markdown

Resolves #3390


Before the change?

  • The github_organization_settings resource and github_organization data source did not surface two attributes that are already modeled on go-github v85's Organization struct and returned by GET/PATCH /orgs/{org} responses.

After the change?

This PR is independent of #3389 and can be reviewed/merged in either order.

Pull request checklist

  • Schema migrations have been created if needed (n/a — additive only)
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

  • Yes
  • No

…hecks_enabled

Surface two attributes that already exist on the upstream go-github v85
Organization struct but were not yet exposed by github_organization_settings:

- default_repository_branch (Organization.DefaultRepositoryBranch)
- secret_scanning_validity_checks_enabled (Organization.SecretScanningValidityChecksEnabled)

Both are also added to the github_organization data source for symmetry.

These fields are returned by GET /orgs/{org} and present in the response
body of PATCH /orgs/{org}, so they are read-back-able. They use Optional
+ Computed so existing configurations that omit them continue to track
the live API value without producing phantom diffs (per the pattern
recommended in integrations#3385).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the Type: Feature New feature or request label May 2, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 2, 2026

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: Feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEAT]: Expose default_repository_branch and secret_scanning_validity_checks_enabled in github_organization_settings

1 participant