-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix typos in DEVELOPMENT.md file #7179
Conversation
|
Hi @shankarpentyala07. Thanks for your PR. I'm waiting for a tektoncd 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/test-infra repository. |
/kind documentation |
/ok-to-test |
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.
could you squash your commits into 1? 🙏
git remote add upstream [email protected]:tektoncd/pipeline.git | ||
``` | ||
|
||
# Optional: Prevent accidental pushing of commits by changing the upstream URL to `no_push` | ||
3. Optional: Prevent accidental pushing of commits by changing the upstream URL to `no_push` | ||
```shell |
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.
Why need this change
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.
Thanks for review
Prior , it is as below:
When copied and pasted in zsh shell , below error is thrown.
# Optional: Prevent accidental pushing of commits by changing the upstream URL to `no_push`
git remote set-url --push upstream no_push
zsh: command not found: no_push
zsh: command not found: #
When optional section is moved to new line as below, the issue is not seen
@@ -271,9 +273,9 @@ The recommended minimum development configuration is: | |||
- 8 GB of (actual or virtualized) platform memory | |||
- Node autoscaling, up to 3 nodes | |||
|
|||
#### Using [KinD](https://kind.sigs.k8s.io/) |
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 remember this was because it stands for K8s in Docker, but I'm ok with either
@@ -353,7 +355,7 @@ While iterating on code changes to the project, you may need to: | |||
- Update your (external) dependencies with: `./hack/update-deps.sh` | |||
- Update your type definitions with: `./hack/update-codegen.sh` | |||
- Update your OpenAPI specs with: `./hack/update-openapigen.sh` | |||
1. Update or [add new CRD types](#adding-new-types) as needed | |||
1. Update or [add new CRD types](#adding-new-crd-types) as needed |
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.
👍
ca0d793
to
b847c6b
Compare
@Yongxuanzhang I have squashed the commits , Could you please review. |
Could you sign the CLA? I remember there is a button there and you need to click it? |
CLA approval in progress. Thanks! |
In optional configuring upstream to no_push in Setup a fork section ,the content was modified to work in zsh shell In Setup a Kubernetes cluster using kind , it was mentioned as Kind in camelcase , changed it to lower case
b847c6b
to
e3d1397
Compare
Closing and reopening the PR to test the CLA 🙃 |
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.
Welcome to the Tekton Community @shankarpentyala07! Thanks for all the changes 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pritidesai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks Preeti for the welcome & all your help,I am hoping to be an active contributor to the project. |
/lgtm |
Closing and reopening the PR to trigger EasyCLA! |
@shankarpentyala07 could you double check if you have signed the CLA? Thanks! |
Thanks @Yongxuanzhang .yes - I did try few times. |
Thanks @Yongxuanzhang .yes - I did try few times. |
Thanks @Yongxuanzhang for identifying the issue. I have opened a new pull request with same changes and CLA passed : #7233. Shall I go ahead and close this pull request and use the new pull request for the changes. |
Yeah, that's fine |
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes