docs: Update documentation with standalone pages by deepsm007 · Pull Request #550 · kubernetes-sigs/prow

deepsm007 · 2025-11-20T15:22:44Z

Add new documentation pages to the Hugo site:

codebase-walkthrough.md: Detailed repository structure and component walkthrough
onboarding.md: Learning path for new contributors
summaries.md: Technical summaries at different levels
faq.md: Frequently asked questions

Add new documentation pages to the Hugo site: - codebase-walkthrough.md: Detailed repository structure and component walkthrough - onboarding.md: Learning path for new contributors - summaries.md: Technical summaries at different levels - faq.md: Frequently asked questions

netlify · 2025-11-20T15:22:50Z

✅ Deploy Preview for k8s-prow ready!

Name	Link
🔨 Latest commit	`e984dec`
🔍 Latest deploy log	https://app.netlify.com/projects/k8s-prow/deploys/691f3247de7eb00008b02bd3
😎 Deploy Preview	https://deploy-preview-550--k8s-prow.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

k8s-ci-robot · 2025-11-20T15:22:52Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: deepsm007
Once this PR has been reviewed and has the lgtm label, please assign droslean for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot · 2025-11-20T15:22:54Z

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

matthyx · 2025-11-20T16:15:32Z

/ok-to-test

stmcginnis · 2025-11-23T12:06:12Z

+
+## Repository Structure
+
+The Prow repository follows a standard Go project layout with clear separation of concerns:


I'm not really sure there is such thing as a "standard" Go project layout. ;)

stmcginnis · 2025-11-23T12:06:47Z

+├── site/                   # Documentation site
+├── test/                   # Test files and test data
+├── hack/                   # Build scripts and utilities
+├── Makefile               # Build automation


Some indentation issues where the comments don't line up. Small thing that's probably fine to leave, but if you do an update it would be good to align them.

stmcginnis · 2025-11-23T12:07:35Z

+title: "Codebase Walkthrough"
+weight: 100
+description: >
+  Detailed explanation of the repository structure and key components


This kind of content always worries me to be included in docs since it's easy for things to get out of sync. But I think this is good with just the top level areas.

stmcginnis · 2025-11-23T12:08:54Z

+
+#### Core Components
+
+**Webhook and Event Handling:**


These are getting into the level of detail that gives me a little more concern about getting out of sync. But I do think this is some useful detail, so maybe worth it.

stmcginnis · 2025-11-23T12:10:19Z

+
+### What programming language is Prow written in?
+
+Primarily Go (94.7%), with some TypeScript (2.5%) for the Deck frontend.


I do not think we need percentages of languages included in docs. Especially since GitHub gives this data automatically.

stmcginnis · 2025-11-23T12:12:36Z

+
+**Deliverable**: Your first merged PR!
+
+## Learning Resources by Topic


I think the scope of this may be getting a little too large for this repo.

k8s-triage-robot · 2026-02-21T13:13:15Z

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle stale
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot · 2026-03-23T13:42:23Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle rotten
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot · 2026-04-22T14:17:37Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Reopen this PR with /reopen
Mark this PR as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot · 2026-04-22T14:17:44Z

@k8s-triage-robot: Closed this PR.

Details

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Reopen this PR with /reopen

Mark this PR as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

k8s-ci-robot requested review from krzyzacy and smg247 November 20, 2025 15:22

k8s-ci-robot added the area/documentation Issues or PRs related to documentation label Nov 20, 2025

k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 20, 2025

k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Nov 20, 2025

k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 20, 2025

stmcginnis reviewed Nov 23, 2025

View reviewed changes

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 21, 2026

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 23, 2026

k8s-ci-robot closed this Apr 22, 2026


		## Repository Structure

		The Prow repository follows a standard Go project layout with clear separation of concerns:


		### What programming language is Prow written in?

		Primarily Go (94.7%), with some TypeScript (2.5%) for the Deck frontend.


		Deliverable: Your first merged PR!

		## Learning Resources by Topic

Conversation

deepsm007 commented Nov 20, 2025

Uh oh!

netlify Bot commented Nov 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for k8s-prow ready!

Uh oh!

k8s-ci-robot commented Nov 20, 2025

Uh oh!

k8s-ci-robot commented Nov 20, 2025

Uh oh!

matthyx commented Nov 20, 2025

Uh oh!

stmcginnis Nov 23, 2025

Choose a reason for hiding this comment

Uh oh!

stmcginnis Nov 23, 2025

Choose a reason for hiding this comment

Uh oh!

stmcginnis Nov 23, 2025

Choose a reason for hiding this comment

Uh oh!

stmcginnis Nov 23, 2025

Choose a reason for hiding this comment

Uh oh!

stmcginnis Nov 23, 2025

Choose a reason for hiding this comment

Uh oh!

stmcginnis Nov 23, 2025

Choose a reason for hiding this comment

Uh oh!

k8s-triage-robot commented Feb 21, 2026

Uh oh!

k8s-triage-robot commented Mar 23, 2026

Uh oh!

k8s-triage-robot commented Apr 22, 2026

Uh oh!

k8s-ci-robot commented Apr 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

netlify Bot commented Nov 20, 2025 •

edited

Loading