feat(setup): complete GitHub App manifest handshake in-app (/api/setup/callback)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- github, java
- Domain
- authentication, backend
Research direction
Read PLAN.md under “Improvement paths A” and inspect install.html, manifest.json, and scripts/GenEnv.java to trace the existing manifest setup flow. Then locate the server entry points for /api/setup and the GitHub App manifest conversion request. Done means the callback exchanges the code, shows a one-time credential setup page, documents GitHub Pages pairing, and leaves no secrets persisted server-side.
Written by the indexing model from the issue text.
Description
Summary
Finish the GitHub App manifest registration flow so operators are not left running gh api …/app-manifests/{code}/conversions and GenEnv.java by hand.
Context
Today install.html posts a manifest to GitHub but redirect_url does not handle the returned code. See PLAN.md → Improvement paths A.
Acceptance criteria
-
redirect_urlininstall.html/manifest.jsonpoints to/api/setup/callback(or equivalent) - Server exchanges
codeviaPOST /app-manifests/{code}/conversionsand presents a one-time setup page (copy credentials / download.env) - Reuse or replace
scripts/GenEnv.javalogic server-side - Document pairing with GitHub Pages hosted install for first-time setup before the bot runs
- No secrets persisted server-side after setup page is shown
Out of scope
- Full migration to
quarkus-github-app(tracked separately)
- Dominant language
- Java
- Stars
- 35
- Forks
- 7
- Avg merge
- 9h 23m
- Merged PRs (30d)
- 154
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from devops-thiago/ThrillhouseBot
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#1093 ·
Maintainers usually reply within 1 day
-
documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
devops-thiago/ThrillhouseBot#321 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#46 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
devops-thiago/ThrillhouseBot#1095 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 58/100
devops-thiago/ThrillhouseBot#1094 ·
Maintainers usually reply within 1 day
All issues in devops-thiago/ThrillhouseBot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NationalSecurityAgency/ghidra#9884 ·
Maintainers usually reply within 2 days
-
Status: Pending Review Type: Feature Request
Difficulty 1/5 Under an hour Newbie friendliness 82/100
OpenRefine/OpenRefine#8019 ·
Maintainers usually reply within 1 day
-
`timer` rule rejects dates the engine acceptsPossibly taken @MFA-G claimed this today. Openbug ready
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
camunda/bpmnlint-plugin-camunda-compat#281 · 3 comments ·
Maintainers usually reply within 1 day
-
status: waiting-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100