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
Clone the Repository
Open Visual Studio Code and click on "Clone Git Repository".
Alternatively, open the terminal and run the following command: git clone https://github.com/MIT-Emerging-Talent/ET6-foundations-group-05.git
Branch Creation
To avoid risking the main branch, we will work on separate branches.
Branch Naming Tips:
Use meaningful names related to your task.
Example: For editing the Learning Goals.md in collaboration folder, name your branch:
Collaboration_Learning_Goals
That way we can easily understand that branch is created for Collaboration/Learning_Goals.md
Avoid using personal or random names to prevent confusion.
Commands for Branch Management:
Check existing branches: git branch
With this command you can see all the branches in a list
Fetch all branches from GitHub: git fetch
With this command you can update your branches from github(if you don't see abranch in your local, use this to see new created branches on github and use git branch again to see new ones)
Create a new branch: git checkout -b "name_of_new_branch"
With this command you will create a new branch and move in that new created branch, that mean yes you can star working on your challenge now...)
After you are done
You need to save and commit and push your changes to github.
Saving Changes Locally
Stage your changes: git add .
Commit your changes with a message: git commit -m "Descriptive message, e.g., Added solution and tests for challenge1"
Push your branch to GitHub: git push origin "branch_name"
Important:
Direct pushes to the main branch are blocked. so you can not use(it won't work) git push origin main
To merge changes into the main branch, you need to create a Pull Request (PR).
-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o--o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-
we didn't work on this part yet so if you don't understand that's because we couldn't explain it, yet:)
Pull Requests and Reviews
Creating a Pull Request (PR)
Before creating a Pull Request, ensure the following:
You have completed all your work on the branch.
All changes have been committed and pushed to GitHub. Once ready, follow these steps:
Create a Pull Request on GitHub.
A teammate will review your Pull Request. During the review, they might approve it or request changes.
Tips for Reviewing:
Before approving or merging a challenge branch, ensure it meets all quality standards and passes the checklist.
The branch owner or reviewer can merge the Pull Request once it's approved.
When the Pull Request is merged, your changes will be added to the main branch. And voilà! Your solution is now part of the main repository. Congratulations!
We’ll cover the detailed steps for creating a Pull Request and conducting reviews later.
Note: Merging a Pull Request always requires a review and approval.(For our repository)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Getting Started with Our Repository in VS Code
Clone the Repository
Open Visual Studio Code and click on "Clone Git Repository".
Alternatively, open the terminal and run the following command:
git clone https://github.com/MIT-Emerging-Talent/ET6-foundations-group-05.git
Branch Creation
To avoid risking the main branch, we will work on separate branches.
Branch Naming Tips:
Use meaningful names related to your task.
Example: For editing the Learning Goals.md in collaboration folder, name your branch:
That way we can easily understand that branch is created for Collaboration/Learning_Goals.md
Avoid using personal or random names to prevent confusion.
Commands for Branch Management:
Check existing branches:
git branch
With this command you can see all the branches in a list
Fetch all branches from GitHub:
git fetch
With this command you can update your branches from github(if you don't see abranch in your local, use this to see new created branches on github and use git branch again to see new ones)
Create a new branch:
git checkout -b "name_of_new_branch"
With this command you will create a new branch and move in that new created branch, that mean yes you can star working on your challenge now...)
After you are done
You need to save and commit and push your changes to github.
Saving Changes Locally
Stage your changes:
git add .
Commit your changes with a message:
git commit -m "Descriptive message, e.g., Added solution and tests for challenge1"
Push your branch to GitHub:
git push origin "branch_name"
Important:
Direct pushes to the main branch are blocked. so you can not use(it won't work) git push origin main
To merge changes into the main branch, you need to create a Pull Request (PR).
-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o--o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-
we didn't work on this part yet so if you don't understand that's because we couldn't explain it, yet:)
Pull Requests and Reviews
Creating a Pull Request (PR)
All changes have been committed and pushed to GitHub.
Once ready, follow these steps:
Create a Pull Request on GitHub.
A teammate will review your Pull Request. During the review, they might approve it or request changes.
Tips for Reviewing:
Before approving or merging a challenge branch, ensure it meets all quality standards and passes the checklist.
The branch owner or reviewer can merge the Pull Request once it's approved.
When the Pull Request is merged, your changes will be added to the main branch. And voilà! Your solution is now part of the main repository. Congratulations!
We’ll cover the detailed steps for creating a Pull Request and conducting reviews later.
Note: Merging a Pull Request always requires a review and approval.(For our repository)
Beta Was this translation helpful? Give feedback.
All reactions