Skip to content

Commit 78ae8bb

Browse files
authored
Merge pull request #134 from advanced-computing/lab-3-updates
Lab 3 updates
2 parents 998d021 + 02e0341 commit 78ae8bb

File tree

1 file changed

+27
-33
lines changed

1 file changed

+27
-33
lines changed

labs/lab_03.md

Lines changed: 27 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -20,28 +20,22 @@ Students:
2020

2121
## [Project team](../docs/project.md#teams) repository setup
2222

23-
1. [Create a public repository in the `advanced-computing` organization.](https://github.com/new?owner=advanced-computing&visibility=public)
24-
- Make the name something distinctive, such as:
25-
- What your project is focused on
26-
- Your celebrity couple name
27-
- A combination of your favorite snacks
28-
- The name your automation will assume once it becomes sentient
29-
1. Using the terminal
30-
1. `cd` to this directory
31-
1. [Clone](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) your project repository
32-
1. Copy the repository URL
33-
1. In the terminal run `git clone <URL>`
34-
1. Open your local repository folder in VSCode
23+
1. [Clone](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) your project repository.
24+
1. Open your local repository folder in VSCode.
25+
1. Create a README that contains your [Proposal](../docs/project.md#proposal) (at a minimum).
26+
1. [Choose a license](https://choosealicense.com/) for your repository.
3527

3628
---
3729

3830
## Adding a [`.gitignore`](https://docs.github.com/en/get-started/getting-started-with-git/ignoring-files#configuring-ignored-files-for-a-single-repository)
3931

40-
- In general, we don't want Git to commit every single file in our local repository
41-
- Examples: **.DS_Store** files in macOS; **Thumbs.db** files in Windows; python environment files **.env** and **.venv** (more on this below)
42-
- We can tell Git which files and folders to ignore using a .gitignore file
32+
- In general, we don't want Git to commit every single file in our local repository. Examples:
33+
- **.DS_Store** files in macOS
34+
- **Thumbs.db** files in Windows
35+
- Python environment files **.env** and **.venv** (more on this below)
36+
- We can tell Git which files and folders to ignore using a `.gitignore` file
4337
- [Set one up for Python and Mac or Windows](https://www.toptal.com/developers/gitignore?templates=macos,python)
44-
- Save a .gitignore file in your repository's root directory
38+
- Save a `.gitignore` file in your repository's root directory
4539

4640
---
4741

@@ -67,29 +61,29 @@ Students:
6761

6862
---
6963

70-
## Checking that .gitignore works
64+
## Checking that `.gitignore` works
7165

72-
- Check the list of changes in the Source Control panel of VSCode
73-
- Go to the .gitignore file, comment the `.venv/` line and save
74-
- Check the list of changes again. Can you see the problem?
75-
- Uncomment the `.venv/` line and save
76-
- Create a new branch, commit and push
77-
- By group, merge one of the pull requests
66+
1. Check the list of changes in the Source Control panel of VSCode.
67+
1. Go to the `.gitignore` file, comment the `.venv/` line and save.
68+
1. Check the list of changes again. Can you see the problem?
69+
1. Uncomment the `.venv/` line and save.
70+
1. Create a new branch, commit and push.
71+
1. By group, merge one of the pull requests.
7872

7973
---
8074

8175
## Pull request practice
8276

83-
- Make sure your repository is up-to-date: `checkout` to the main branch and `pull`
84-
- Each student will create a new branch to add a new feature:
85-
- **Student A**: add the notebook from [Part 1](../docs/project.md#part-1)
86-
- Ensure the notebook runs from VSCode.
87-
- The notebook may not (fully) render on GitHub, due to having interactivity. Try accessing the GitHub URL via [nbviewer](https://nbviewer.org/)/[Colab](https://colab.research.google.com/).
88-
- **Student B**: add a README.md
89-
- Add project title and a short description
90-
- Setup/usage instructions - these will change over time
91-
- **Student A or B**: add an [Open in Colab button](https://openincolab.com/)
92-
- Review each other's pull requests
77+
1. Make sure your repository is up-to-date: `checkout` to the `main` branch and `pull`
78+
1. Each student will create a new branch to add a new feature:
79+
1. **Student A**: add the notebook from [Part 1](../docs/project.md#part-1)
80+
- Ensure the notebook runs from VSCode.
81+
- The notebook may not (fully) render on GitHub, due to having interactivity. Try accessing the GitHub URL via [nbviewer](https://nbviewer.org/)/[Colab](https://colab.research.google.com/).
82+
1. **Student B**: add a `README.md`.
83+
- Add project title and a short description
84+
- Setup/usage instructions - these will change over time
85+
1. **Student A or B**: add an [Open in Colab button](https://openincolab.com/)
86+
1. Review each other's pull requests
9387

9488
---
9589

0 commit comments

Comments
 (0)