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
4. Now you have a local copy of this repo! Make some changes. Correct your name in the "students.txt" file (on your machine, not on GitHub).
12
12
5. Add the file to the upcoming commit from the terminal: `git add students.txt`
13
-
6. Add a useful message that summarizes your changes: `
13
+
6. Add a useful message that summarizes your changes. Either add a message directly in the command line with
14
14
```bash
15
-
git commit -m "<summary>"
15
+
git commit -m "<Very useful commit message>"
16
+
```
17
+
or set the default commit message editor to be your editor of choice:
18
+
```bash
19
+
git config --global core.editor "<your favorite editor, such as vim>"
16
20
```
17
21
7. Push your changes from your local environment to your fork on GitHub:
18
22
```bash
@@ -37,14 +41,7 @@ In Python,
37
41
python -m pytest
38
42
```
39
43
40
-
4. Once the bug is fixed, commit your changes with `git commit` and a useful message. Either add a message directly in the command line with
41
-
```bash
42
-
git commit -m "<Very useful commit message>"
43
-
```
44
-
or set the default commit message editor to be your editor of choice:
45
-
```bash
46
-
git config --global core.editor "<your favorite editor, such as vim>"
47
-
```
44
+
4. Once the bug is fixed, commit your changes with `git commit` and a useful message.
48
45
49
46
5. When pushing, git will ask you to specify which remote you want to push to, with the `git push --set-upstream origin quadfix-<your-name>` command. This specifies that you want your repository on GitHub (the remote called "origin") to have a new branch with the same name as your local branch.
50
47
6. Submit a pull request to the `main` branch. We'll review and merge later.
0 commit comments