You’re viewing Paradaux’s public workspaceSign in to vote Get taskl.ie for your team

PAR-459

Loading issues

PAR-459 · QA: first-time GitHub connection is blocked by missing… · Paradaux · taskl.ie

PAR-459· sub-issue of PAR-457

QA: first-time GitHub connection is blocked by missing installation link and manual ID setup

Part of QA PAR-457. Confirmed in live production 18 Oct, desktop and mobile. Journey: new workspace → onboarding Connect GitHub → Open settings → expand '+ Connect an installation'. Neither onboarding nor GitHub settings offers a GitHub App installation URL. Settings instead requires 'Installation ID' and says to copy it from GitHub's installation settings URL. A first-time owner has never installed the app and has no way here to discover which app to install. 'Continue' in onboarding advances identically to Skip without establishing a connection. Impact: the promised automatic PR/deployment journey cannot be started from the product. Expected: install/authorize CTA, callback binding installation to workspace, visible verified connection state, and return to setup. If deployment lacks configuration, show actionable unavailability rather than exposing a manual internal identifier as the primary path. URLs: /onboarding?w=design-qa-20261018&step=github and /w/design-qa-20261018/settings/github.

Activity

taskl.ie created the issue 5d ago
taskl.ie edited the description 5d ago
View changes
Removed: Part of QA PAR-457. Live 18 Oct at 390×844. Create workspace → skip Discord → Connect GitHub. Copy says 'Install the GitHub app', but only action is 'Open settings' linking to /settings/github. 'Skip for now' and 'Continue' advance identically without a connection. Expected: direct installation or explicit unavailable state, verified connection state, and return to onboarding. Settings destination to be checked in this audit.
Added: Part of QA PAR-457. Confirmed in live production 18 Oct, desktop and mobile. Journey: new workspace → onboarding Connect GitHub → Open settings → expand '+ Connect an installation'. Neither onboarding nor GitHub settings offers a GitHub App installation URL. Settings instead requires 'Installation ID' and says to copy it from GitHub's installation settings URL. A first-time owner has never installed the app and has no way here to discover which app to install. 'Continue' in onboarding advances identically to Skip without establishing a connection. Impact: the promised automatic PR/deployment journey cannot be started from the product. Expected: install/authorize CTA, callback binding installation to workspace, visible verified connection state, and return to setup. If deployment lacks configuration, show actionable unavailability rather than exposing a manual internal identifier as the primary path. URLs: /onboarding?w=design-qa-20261018&step=github and /w/design-qa-20261018/settings/github.
taskl.ie5d ago
Implementation now provides a state-bound GitHub App installation/callback flow and an honest unavailable state. Production configuration check: the existing backend credential identifies the GitHub App as tesks-dev (display name Tesks (DEV)); the UI secret currently has no App slug. Rollout must set GITHUB_APP_SLUG=tesks-dev for the current App and configure its setup URL to https://app.taskl.ie/github/setup, or replace this with the intended production App. No GitHub App permissions or production credentials were changed.
taskl.ie5d ago
Implemented in the dependent QA stack: https://github.com/ParadauxIO/taskl.ie/pull/89

Combined verification passed: full API suite (1,306 tests), web lint and TypeScript, unit suite (1,211 passed; one existing skip), 483 Chromium story checks, and the production Next.js/CSS build. Desktop/mobile component evidence and a flow diagram are attached where applicable; server-rendered screenshot gaps and GitHub rollout prerequisites are explicit in the PR.

Awaiting review and merge; production application code has not been deployed by this task.
taskl.ie changed status from In progress to Done 4d ago

Workspace permission required to comment

Comments and reactions require workspace permission. Ask a workspace owner or admin for access. You can sign in to vote.