Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the repository README, which provides instructions and context for learning how to fork and open pull requests on GitHub.
Changes:
- Removes most of the README’s instructional paragraphs and links.
- Replaces the removed section with a single modified line (currently truncated and containing a typo).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| After forking this repository, you can make some changes to the project, and submit [a Pull Request](https://github.com/octocat/Spoon-Knife/pulls) as practice. | ||
|
|
||
| For some more information on how to fork a repository, [check out our guide, "Forking Projects""](http://guides.github.com/overviews/forking/). Thanks! :sparkling_heart: | ||
| Creating a *fork* is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit *Pull Requests* to help make other people's projects bettek a repository, |
There was a problem hiding this comment.
The sentence now contains a typo: "bettek" should be "better".
| Creating a *fork* is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit *Pull Requests* to help make other people's projects bettek a repository, | |
| Creating a *fork* is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit *Pull Requests* to help make other people's projects better a repository, |
| After forking this repository, you can make some changes to the project, and submit [a Pull Request](https://github.com/octocat/Spoon-Knife/pulls) as practice. | ||
|
|
||
| For some more information on how to fork a repository, [check out our guide, "Forking Projects""](http://guides.github.com/overviews/forking/). Thanks! :sparkling_heart: | ||
| Creating a *fork* is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit *Pull Requests* to help make other people's projects bettek a repository, |
There was a problem hiding this comment.
Line 5 reads as an incomplete/garbled sentence ("...projects bettek a repository,") and the README now ends mid-thought after removing the explanatory paragraphs. Please restore the intended wording so the introduction is grammatically complete and retains the guidance content (or replace it with an equivalent complete section).
| Creating a *fork* is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit *Pull Requests* to help make other people's projects bettek a repository, | |
| Creating a *fork* means producing a personal copy of someone else's project here on GitHub. Forks act as a bridge between the original repository and your copy: you can freely experiment with changes in your fork and, when you're ready, submit *pull requests* to propose improvements back to the original project. | |
| Use this repository as a safe place to practice the workflow of forking, cloning, making changes, and opening pull requests before contributing to other projects. |
| After forking this repository, you can make some changes to the project, and submit [a Pull Request](https://github.com/octocat/Spoon-Knife/pulls) as practice. | ||
|
|
||
| For some more information on how to fork a repository, [check out our guide, "Forking Projects""](http://guides.github.com/overviews/forking/). Thanks! :sparkling_heart: | ||
| Creating a *fork* is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit *Pull Requests* to help make other people's projects bettek a repository, |
There was a problem hiding this comment.
The PR description says this is a "small edit", but this change removes most of the README’s instructional content and leaves only a truncated line. If the intent was only a small edit, consider reverting the deletions; if the intent is to shorten the README, please update the PR description to match and ensure the remaining text is complete.
I added a small edit to README file.