📝 Fix misspelling & missing punctuation mark in Pull Request Handbook Documentation. #36709
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
octavia-squidington-iii
added
area/documentation
natikgadzhi
approved these changes
Apr 1, 2024
|
Thank you again! Please don't hesitate to send more of those fixes, and/or ping me or anyone on the team if you need any help, @chelmerrox. |
nurikk
pushed a commit
to nurikk/airbyte
that referenced
this pull request
Apr 4, 2024
markcusack
pushed a commit
to markcusack/airbyte
that referenced
this pull request
Apr 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
There is a misspelling/typo and a missing punctuation in the Pull Request Handbook documentation. It can be found as the second last sentence under the first sub-heading: Pull Request Title Convention.
If you're code change is doing more than one change type at once we strongly recommend to break into multiple pull requests. It helps us to review and merge your contribution.Fixes/Solution:
I've fixed the problems for more readability. I've replaced you're with your & added a comma after the word once.
If your code change is doing more than one change type at once, we strongly recommend to break into multiple pull requests. It helps us to review and merge your contribution.Thanks in advance for you feedback!