jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

Fix for md049 consistent emphasis (#38201)

Browse Source 
Co-authored-by: Jess Hosman <1183847+jhosman@users.noreply.github.com>
This commit is contained in:
Grace Park
2023-06-21 11:10:23 -07:00
committed by GitHub
parent 638de9b7da
commit 4545543862
224 changed files with 670 additions and 670 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/get-started/using-git/about-git-rebase.md
View File

@@ -98,7 +98,7 @@ Breaking this information, from top to bottom, we see that:
- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state.
- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom).
- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository.
- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are _rebased_ onto your repository.
- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`).
- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits.

2
content/get-started/using-git/getting-changes-from-a-remote-repository.md
View File

@@ -44,7 +44,7 @@ such remote-tracking branch names to `origin/foo`.
## Fetching changes from a remote repository
Use `git fetch` to retrieve new work done by other people. Fetching from a repository grabs all the new remote-tracking branches and tags *without* merging those changes into your own branches.
Use `git fetch` to retrieve new work done by other people. Fetching from a repository grabs all the new remote-tracking branches and tags _without_ merging those changes into your own branches.
If you already have a local repository with a remote URL set up for the desired project, you can grab all the new information by using `git fetch *remotename*` in the terminal:

2
content/get-started/using-git/pushing-commits-to-a-remote-repository.md
View File

@@ -92,7 +92,7 @@ your local Git clone:
git remote add upstream THEIR_REMOTE_URL
```
Now, you can fetch updates and branches from *their* fork:
Now, you can fetch updates and branches from _their_ fork:
```shell
git fetch upstream

2
content/get-started/using-git/using-git-rebase-on-the-command-line.md
View File

@@ -92,7 +92,7 @@ edit dd1475d something I want to split
reword 4ca2acc i cant' typ goods
```
Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It _also_ processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal: