| Age | Commit message (Collapse) | Author |
|---|
|
When contributing specific parts of k8s, its helpful to know how to slice the build to only build a certain binary.
|
|
Describe new labels in triage guidelines
|
|
Recently we have added new labels to identify issues that are candidates for close.
These issues are typically the one which are not goint to close via a fix. Add
description in triage guidelines about when to use these labels.
Related PR is,
kubernetes/test-infra#7554
|
|
The issue triage doc has moved from:
contributors/devel/issues.md
to:
contributors/guide/issue-triage.md
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
Add code search and contributor guide, remove reviewable
|
|
|
|
Recently we have added new labels to identify issues that are candidates for close.
These issues are typically the one which are not goint to close via a fix. Add
description in triage guidelines about when to use these labels.
Related PR is,
https://github.com/kubernetes/test-infra/pull/7554
|
|
Mac OS X was renamed to OS X in 2012, and then renamed again to macOS in 2016.
I suggest that the current name (macOS) should be used whenever referencing the Apple OS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Edited for grammar, sentence structure, punctuation and general clarity.
|
|
|
|
|
|
|
|
|
|
|
|
Add mention of membership roles to contrib guide
|
|
|
|
|
|
Cleanup and move to /contributors/guide of pull requests doc
|
|
Minor cleanup in pull-requests.md
|
|
Pinging someone with a github mention is different from using a bot command to assign them as a reviewer. This commit includes a specific explanation.
|
|
This addresses a few broken links that resulted from style changes.
|
|
|
|
|
|
If a contributor reads the pull request template upon creating a PR then
they will get hints, but ahead of a PR there has not been sufficient
documentation of when release notes are required for a change, how a
contributor should indicate that a change needs notes, or what the note
text should be. To help address this, this commit adds a first set of
release notes documentation for reference by the contributor guide.
|
|
Links now point at new location for pull-requests.md.
|
|
The pull-requests.md document has gotten quite out of date. This commit
does a massive scrub of its content for completeness, accuracy and
readability. A number of links are fixed, updated information on labels
and bot commands is added, workflow descriptions for test and merge are
updated, and a description of the KEP process is added.
|
|
Understanding the pull request process is central to being a successful
contributor. This commit moves it from the more technical k8s internals
detailed devel/ area over to the guide/ where it will get more
visibility.
This patch just moves the file and leaves a tombstone reminder
behind.
|
|
Thanks were expressed twice in the Contributor Guide. To remove clutter, this pull request removes this section from the main README but leaves it in community-expectations.md. In the future, code review documentation will be added as well.
|
|
|
|
Added a new section in the README for things that are important for
contributors to know, but not something they will use often or at all
but needs to be documented, like owners files.
Linked to documentation team's contribution page.
|
|
Contains example for adding a SIG label
|
|
The table of contents has slipped out of date.
FYI I'm generating a ToC with a command like:
pandoc -t markdown_github --toc -s README.md
and then picking up the modifications and dropping them in the document.
Not the best workflow, but..markdown.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
|
|
|
|
|
|
|
|
|
|
Add TOC headers to contributor, developer, and mentorship guides
|
|
This adds the necessary metadata to generate a table of contents when
when generating these pages for the documentation.
|
|
Communication resources are in their own directory, this points people
to it.
|
|
Even the existing one is working, the updated is more correct.
|
