Docs: Updated README with note section regarding the avoidance of edi… #70213
Conversation
…ting multiple lines In "Making necessary changes," I added a note stating not to make multiple changes in the file and provided a link to the "Design decisions for the tutorials "
|
I'm having problems with the pull request I still haven't been able to accomplish a pull request is it possible for me to get some assistance on pulling request ID really APPERICATE it if so my name is Jennifer Jackson and email is *** and number is *** thanks |
Hey @Jcolebeyond02, welcome to your first contribution! Don't worry, I've got you covered. We have a section in the documentation with straightforward and easy-to-follow steps to help you get started with your pull request. Just follow the tutorial located here. If you find any difficulties or get stuck at any point, feel free to reach out to me. I'm here to help.
happy coding. |
|
@Jcolebeyond02, I want to reiterate what @Esh07 mentioned. Don't share your personal info. I've updated your comment to remove it. In terms of getting help try the following
|
| @@ -134,6 +134,7 @@ For example: | |||
| git switch -c add-alonzo-church | |||
| ``` | |||
| ## Make necessary changes and commit those changes | |||
| > **Important**: Please DO NOT change multiple lines. Here's why - [read the 3rd bullet point](https://github.com/firstcontributions/first-contributions/issues/35892#issue-778716847). | |||
There was a problem hiding this comment.
I'd rather not add another note to the Readme that's specific about our project. I think it's better handled with checks in merge script.
…ting multiple lines
In "Making necessary changes," I added a note stating not to make multiple changes in the file and provided a link to the "Design decisions for the tutorials "
@Roshanjossey, what are your thought on these changes?