Adding GPT Actions example for GitHub OAuth

[ChrisCarini]

Summary

Adding GPT Actions example for GitHub OAuth.

Motivation

The current cookbook example, "GPT Actions library - GitHub", uses a PAT for authentication. Because PAT authentication is used, this relies on whatever access the original PAT author (likely the GPT creator) has, and does not lend towards being usable by a large audience (i.e. if a GPT creator wants to share their GPT more broadly).

Testing

• Previewed in GitHub UI (ref), everything appeared 'as expected'.
• Screenshots have been included for each of the steps, confirming everything works 'as expected'. Additionally, secrets et cetera were not scrubbed so it would be easier to follow, but both the GPT and GitHub App have been deleted prior to this PR branch being pushed, so there should be no concern of leakage.

---

For new content

When contributing new content, read through our contribution guidelines, and mark the following action items as completed:

• I have added a new entry in registry.yaml (and, optionally, in authors.yaml) so that my content renders on the cookbook website.
• I have conducted a self-review of my content based on the contribution guidelines:
  • Relevance: This content is related to building with OpenAI technologies and is useful to others.
  • Uniqueness: I have searched for related examples in the OpenAI Cookbook, and verified that my content offers new insights or unique information compared to existing documentation.
  • Spelling and Grammar: I have checked for spelling or grammatical mistakes.
  • Clarity: I have done a final read-through and verified that my submission is well-organized and easy to understand.
  • Correctness: The information I include is correct and all of my code executes successfully.
  • Completeness: I have explained everything fully, including all necessary references and citations.

We will rate each of these areas on a scale from 1 to 4, and will only accept contributions that score 3 or higher on all areas. Refer to our contribution guidelines for more details.

Note from @ChrisCarini - the contribution guidelines are pretty bare. Should the old ones be brought back? 😅

[chatgpt-codex-connector]

💡 Codex Review

openai-cookbook/images/gpt_action_github_oauth/generate_client_secret_after.png

Line 1 in 1629f08

�PNG

Remove exposed GitHub OAuth client secret from screenshot

This screenshot contains a readable GitHub App Client secret, which is a credential disclosure in git history. Even if the app was later deleted, leaked secrets can still be harvested from forks/caches and should be treated as compromised; please replace this image with a redacted version and rotate/revoke the credential before publishing.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[ChrisCarini]

💡 Codex Review

openai-cookbook/images/gpt_action_github_oauth/generate_client_secret_after.png

Line 1 in 1629f08

�PNG

Remove exposed GitHub OAuth client secret from screenshot
This screenshot contains a readable GitHub App Client secret, which is a credential disclosure in git history. Even if the app was later deleted, leaked secrets can still be harvested from forks/caches and should be treated as compromised; please replace this image with a redacted version and rotate/revoke the credential before publishing.

ℹ️ About Codex in GitHub

One step ahead of ya 😉 👇

Additionally, secrets et cetera were not scrubbed so it would be easier to follow, but both the GPT and GitHub App have been deleted prior to this PR branch being pushed, so there should be no concern of leakage.