l3montree-dev / l3montree-dev/devguard
Add Pipeline Awaiting Status Indicator After Auto-Setup Completion
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
Summary
After all four Auto-Setup checks turn green, the user is left on the setup screen with no feedback about what happens next. In reality, the DevGuard pipeline has been triggered and is actively running — but this is invisible to the user. First scan results typically take 2–3 minutes to arrive. This creates an ambiguous state where the user doesn't know whether to wait, navigate away, or refresh manually.
Proposed Solution
1. Add a 5th Status Item: "Pipeline is running"
Directly below the four existing green checkmarks, add a fifth item with a loading/spinner indicator while the pipeline is executing:
✅ Project Webhook is created
✅ Project variables are created
✅ The pipeline is created. A new branch was pushed to the repository
✅ A merge request is created
⏳ Waiting for first scan results...
2. Transition to Green + Automatic Redirect
Once the backend signals that first scan results are available, the 5th item turns green — just like the other four checks. The frontend then automatically redirects the user to the project overview without any manual interaction required.
✅ Project Webhook is created
✅ Project variables are created
✅ The pipeline is created. A new branch was pushed to the repository
✅ A merge request is created
✅ First scan results are available → [auto-redirect to overview]
Why This Matters
- Users currently have no indication that anything is still happening after the 4 green checks
- Without feedback, users are likely to navigate away prematurely or assume the tool is idle
- The transition from setup → results is a high-value moment in the onboarding flow and should feel seamless
Related
Closes / relates to: https://github.com/l3montree-dev/devguard/issues/2100
Contributor 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.
Research direction
Start by tracing the setup screen's completion state and the signal that first scan results are available; the issue names no files or tests, so locate those entry points in the repository. Done means the fifth status item shows while the pipeline runs, turns green when results arrive, and automatically redirects to the project overview.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100