-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: 📝 add learning objectives to
Git and GitHub
session (#97)
## Description This PR adds the learning objectives for the "Review of Git and GitHub" session. Closes #63 <!-- Please delete as appropriate: --> This PR needs an in-depth review. ## Checklist - [X] Ran spell-check - [X] Formatted Markdown - [X] Rendered website locally --------- Co-authored-by: Luke W. Johnston <[email protected]>
- Loading branch information
1 parent
35a0a61
commit 9cf3145
Showing
1 changed file
with
50 additions
and
1 deletion.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,50 @@ | ||
# Review of Git and GitHub {#sec-git-and-github} | ||
# Review of Git and GitHub {#sec-git-and-github} | ||
|
||
<!-- TODO: Add an introduction here --> | ||
|
||
## Learning objectives | ||
|
||
This session’s **overall learning outcome** is to enable you to: | ||
|
||
1. Describe the core concepts and functionalities of Git and GitHub and | ||
describe their role in facilitating effective collaboration, then use | ||
some of the basic functionality of Git and GitHub on a shared repository. | ||
|
||
**Specific objectives** are to: | ||
|
||
1. Explain the concept of formal **version control** and its key | ||
benefits. | ||
2. Describe what a **repository** is in the context of Git and GitHub, | ||
including the difference between **local** and **remote** | ||
repositories, and then create a new repository in a way that you | ||
can work on it with a team. | ||
3. Explain the role of **branching** in managing parallel work and | ||
create a few branches on a team repository. | ||
4. Explain how **commits** are used to track changes and maintain a | ||
history of files, and then to commit some changes in the branches | ||
on the team repository. | ||
5. Describe how **pull requests** are used to integrate changes and | ||
collaborate with team members, then to create them on the team | ||
repository from the branches that you already committed changes to. | ||
6. Describe how GitHub **issues** can be used for managing tasks and | ||
make a few of them on your team GitHub repository. | ||
7. Discuss and explain how Git and GitHub facilitate collaboration by: | ||
- Coordinating changes between multiple contributors. | ||
- Tracking contributions and changes over time. | ||
- Encouraging transparency and accountability in projects. | ||
|
||
## TODO: Section | ||
|
||
::: callout-note | ||
## Reading task: \~4 minutes | ||
|
||
TODO: Reading text | ||
::: | ||
|
||
## Exercise: TODO: Add title | ||
|
||
> Time: \## minutes. | ||
## Summary | ||
|
||
- TODO: List of summary items |