You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- GitHub & Git
- Introduction to Git
- Introduction to GitHub
- Getting Started with Git and GitHub
- VS Code
The "Getting Started with Git and GitHub" section starts with:
To get started with Git and GitHub, follow these steps:
There are instructions to setup Git, but no instruction to sign-up for GitHub.
This section has a subsection of "Practicing Contributing with VS Code" which content a tutorial to create and clone a repo, make changes, and push them to GitHub.
However, the section "VS Code" is right after this subsection. So, it doesn't make sense to practice on VS Code before explaining it.
Suggested Solution
Add an instruction to sign up for GitHub in the "Getting Started with Git and GitHub" section.
Move the "Practicing Contributing with VS Code" subsection right after "VS Code" section and make it the same heading level as "Getting Started with Git and GitHub" and "VS Code".
The text was updated successfully, but these errors were encountered:
I would also suggest including in the documentation that while creating a new repository is recommended for open source contributions, forking the repository can remain an option as well. This approach offers flexibility for contributors and encourages collaboration. I fully support your idea of opening up the project to external contributors.
Description
In the "Tools to be Successful" chapter, we have this structure of sections:
The "Getting Started with Git and GitHub" section starts with:
There are instructions to setup Git, but no instruction to sign-up for GitHub.
This section has a subsection of "Practicing Contributing with VS Code" which content a tutorial to create and clone a repo, make changes, and push them to GitHub.
However, the section "VS Code" is right after this subsection. So, it doesn't make sense to practice on VS Code before explaining it.
Suggested Solution
The text was updated successfully, but these errors were encountered: