-
Notifications
You must be signed in to change notification settings - Fork 160
docs: Update overview page with comprehensive Prow introduction #553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Enhance the overview page with detailed information about: - What problem Prow solves - Who Prow is for (primary users and skill levels) - Comprehensive key features (job execution, webhooks, plugins, Tide, Deck, Spyglass, etc.) - Integration support details Preserves existing valuable content about Prow in the wild and useful talks.
✅ Deploy Preview for k8s-prow ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: deepsm007 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hi @deepsm007. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
|
Nice clarification - I could see this being useful for anyone new to the project to help understand its purpose. /lgtm |
petr-muller
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not exactly a fan of the "header and 3-5 bullets" that the LLMs tend to prefer but I think having structured approachable content like this is better than no content.
There are some imprecise statements (commented inline) thought that I think should be fixed.
| - **Code Review Automation**: Automate repetitive review tasks and enforce project policies | ||
| - **Project Management**: Automate issue management, labeling, and project workflows | ||
| - **Scalability**: Handle thousands of repositories and millions of test runs | ||
| - **Integration**: Integrate with GitHub, Gerrit, and other code hosting platforms |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we have integration with anything else than GH and gerrit
| - **Presubmit Jobs**: Run on pull requests before merge | ||
| - **Postsubmit Jobs**: Run after code is merged | ||
| - **Periodic Jobs**: Run on a schedule (cron-based) | ||
| - **Batch Jobs**: Run multiple jobs in parallel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not true, batch jobs test multiple PRs at once before merge to ensure they are compatible with each other
| Deck provides a web interface for: | ||
| - Viewing job status and history | ||
| - Browsing test results and logs | ||
| - Managing Prow configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we have this
Enhance the overview page with detailed information about:
Preserves existing valuable content about Prow in the wild and useful talks.