Skip to content

docs: clarify GitHub OAuth vs GitHub App setup and required app settings#300

Open
brone1323 wants to merge 1 commit into
hcengineering:mainfrom
brone1323:docs/improve-github-integration-guide
Open

docs: clarify GitHub OAuth vs GitHub App setup and required app settings#300
brone1323 wants to merge 1 commit into
hcengineering:mainfrom
brone1323:docs/improve-github-integration-guide

Conversation

@brone1323

@brone1323 brone1323 commented May 11, 2026

Copy link
Copy Markdown

Summary

Addresses confusion reported in #296 and #297 where users spent hours debugging the GitHub integration because:

  1. Two different GitHub app types share the same env var name — the OAuth App (for sign-in) and the GitHub App (for issue sync) both use GITHUB_CLIENT_SECRET, but for different services. Added a callout box at the top of each section making this explicit, and added a concrete yaml snippet showing which service gets which variables.
  2. Three required GitHub App checkboxes were undocumented — users had to discover by trial-and-error that "Expire user authorization tokens", "Request user authorization (OAuth) during installation", and "Redirect on update" must all be enabled. Added these as an explicit checklist with a recovery note for users who already created the app without them.

Changes

  • README.md: Added [!NOTE] callout to GitHub OAuth section clarifying it uses a GitHub OAuth App (not a GitHub App), with variable names shown in a yaml block
  • README.md: Added [!NOTE] callout to GitHub Service section with the same disambiguation
  • README.md: Split GitHub Service Prerequisites into "Required GitHub App settings" and "Credentials to collect" subsections; listed the three mandatory checkboxes with an [!IMPORTANT] recovery path

Test plan

  • Read both sections end-to-end and confirm the OAuth App vs GitHub App distinction is clear
  • Verify yaml snippets are syntactically valid
  • Confirm no existing correct information was removed

- Add a note distinguishing GitHub OAuth App (sign-in) from GitHub App
  (GitHub Service / issue sync), since both use a GITHUB_CLIENT_SECRET
  env var with different names, which has caused user confusion (hcengineering#296, hcengineering#297)
- Add yaml snippet showing exactly which service gets GITHUB_CLIENT_ID
  and GITHUB_CLIENT_SECRET for OAuth
- Document the three required GitHub App checkboxes that must be enabled
  during app creation (Expire user authorization tokens, Request user
  authorization during installation, Redirect on update) and the
  uninstall/reinstall recovery path if they were missed (hcengineering#297)
- Restructure GitHub App Prerequisites into subsections for clarity
@huly-github-staging

Copy link
Copy Markdown

Connected to Huly®: SELFH-299

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant