docs: add UI onboarding guides for GitHub, GitLab, and Forgejo compon…#599
docs: add UI onboarding guides for GitHub, GitLab, and Forgejo compon…#599MartinBasti wants to merge 1 commit intokonflux-ci:mainfrom
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
🚀 Preview is available at: https://pr-599--konflux-docs.netlify.app |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request restructures the component onboarding documentation by introducing detailed UI-based procedures for GitHub, GitLab, and Forgejo. It updates the navigation labels and refactors the main 'Creating' page to link directly to these provider-specific UI and CLI guides. Review feedback focuses on correcting the spelling of 'dialogue' to 'dialog' across several files for technical consistency and suggests rephrasing a step in the GitHub guide to maintain stylistic consistency with the other onboarding documents.
…ents Split component onboarding docs into separate per-provider guides covering both UI and CLI, improving UX by removing the need for users to mentally skip provider-specific steps that don't apply to them. This mirrors the existing CLI section structure and makes each provider's guide self-contained and directly linkable. - Add UI procedures to creating-github, creating-gitlab, creating-forgejo - Include inline source secret creation steps for GitLab/Forgejo UI flow - Document Git provider annotation and Git url annotation fields - Simplify creating.adoc to link to per-provider guides via tables - Remove redundant secret requirement mentions from the main page - Add GitHub App installation prerequisite note for GitHub provider Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
🚀 Preview is available at: https://pr-599--konflux-docs.netlify.app |
1 participant
…ents
Split component onboarding docs into separate per-provider guides covering both UI and CLI, improving UX by removing the need for users to mentally skip provider-specific steps that don't apply to them. This mirrors the existing CLI section structure and makes each provider's guide self-contained and directly linkable.