Skip to content

Commit 86a4bea

Browse files
authored
Revert "Updates to image pathing" (#719)
* Revert "Updates to image pathing (#716)" This reverts commit 36751c8. * Use markdown syntax for images ![alt](path)
1 parent 36751c8 commit 86a4bea

4 files changed

+13
-13
lines changed

.github/steps/1-create-a-branch.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -21,23 +21,23 @@ Branches allow you to separate your work from the `main` branch. In other words,
2121

2222
**What is a profile README?**: A _[profile README](https://docs.github.com/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme)_ is essentially an "About me" section on your GitHub profile where you can share information about yourself with the community on GitHub.com. GitHub shows your profile README at the top of your profile page. For more information, see "[Managing your profile README](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme)".
2323

24-
![profile-readme-example](../../images/profile-readme-example.png)
24+
![profile-readme-example](/images/profile-readme-example.png)
2525

2626
### :keyboard: Activity: Your first branch
2727

2828
1. Open a new browser tab and navigate to your newly made repository. Then, work on the steps in your second tab while you read the instructions in this tab.
2929
2. Navigate to the **< > Code** tab in the header menu of your repository.
3030

31-
![code-tab](../../images/code-tab.png)
31+
![code-tab](/images/code-tab.png)
3232

3333
3. Click on the **main** branch drop-down.
3434

35-
![main-branch-dropdown](../../images/main-branch-dropdown.png)
35+
![main-branch-dropdown](/images/main-branch-dropdown.png)
3636

3737
4. In the field, name your branch `my-first-branch`. In this case, the name must be `my-first-branch` to trigger the course workflow.
3838
5. Click **Create branch: my-first-branch** to create your branch.
3939

40-
![create-branch-button](../../images/create-branch-button.png)
40+
![create-branch-button](/images/create-branch-button.png)
4141

4242
The branch will automatically switch to the one you have just created.
4343
The **main** branch drop-down bar will reflect your new branch and display the new branch name.

.github/steps/2-commit-a-file.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The following steps will guide you through the process of committing a change on
2323

2424
2. Select the **Add file** drop-down and click **Create new file**.
2525

26-
![create new file option](../../images/create-new-file.png)
26+
![create new file option](/images/create-new-file.png)
2727

2828
3. In the **Name your file...** field, enter `PROFILE.md`.
2929

@@ -33,11 +33,11 @@ The following steps will guide you through the process of committing a change on
3333
Welcome to my GitHub profile!
3434
```
3535

36-
![profile.md file screenshot](../../images/my-profile-file.png)
36+
![profile.md file screenshot](/images/my-profile-file.png")
3737

3838
5. Click **Commit changes...** in the upper right corner above the contents box. For commits, you can enter a short commit message that describes what changes you made. This message helps others know what's included in your commit. GitHub offers a simple default message, but let's change it slightly for practice. First, enter `Add PROFILE.md` in the first text-entry field titled "Commit message".
3939

40-
![screenshot of adding a new file with a commit message](../../images/commit-full-screen.png)
40+
![screenshot of adding a new file with a commit message](/images/commit-full-screen.png")
4141

4242
6. In this lesson, we'll ignore the other fields and click **Commit changes**.
4343
7. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.

.github/steps/3-open-a-pull-request.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Now that you have made a change to the project and created a commit, it’s time
1818

1919
You may have noticed after your commit that a message displayed indicating your recent push to your branch and providing a button that says **Compare & pull request**.
2020

21-
![screenshot of message and button](../../images/compare-and-pull-request.png)
21+
![screenshot of message and button](/images/compare-and-pull-request.png)
2222

2323
To create a pull request automatically, click **Compare & pull request**, and then skip to step 6 below. If you don't click the button, the instructions below walk you through manually setting up the pull request.
2424

@@ -27,18 +27,18 @@ To create a pull request automatically, click **Compare & pull request**, and th
2727
3. In the **base:** dropdown, make sure **main** is selected.
2828
4. Select the **compare:** dropdown, and click `my-first-branch`.
2929

30-
![screenshot showing both branch selections](../../images/pull-request-branches.png)
30+
![screenshot showing both branch selections](/images/pull-request-branches.png")
3131

3232
5. Click **Create pull request**.
3333
6. Enter a title for your pull request. By default, the title will automatically be the name of your branch. For this exercise, let's edit the field to say `Add my first file`.
3434
7. The next field helps you provide a description of the changes you made. Here, you can add a description of what you’ve accomplished so far. As a reminder, you have: created a new branch, created a file, and made a commit.
3535

36-
![screenshot showing pull request](../../images/Pull-request-description.png)
36+
![screenshot showing pull request](/images/Pull-request-description.png)
3737

3838
8. Click **Create pull request**. You will automatically be navigated to your new pull request.
3939
9. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
4040

4141
> [!NOTE]
4242
> You may see evidence of GitHub Actions running on the tab with the pull request opened! The image below shows a line you might see on your pull request after the Action finishes running.
4343
>
44-
> ![screenshot of an example of an actions line](../../images/Actions-to-step-4.png)
44+
> ![screenshot of an example of an actions line](/images/Actions-to-step-4.png)

.github/steps/4-merge-your-pull-request.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ You successfully created a pull request. You can now merge your pull request.
1515

1616
As noted in the previous step, you may have seen evidence of GitHub Actions running which automatically progresses your instructions to the next step. You'll have to wait for it to finish before you can merge your pull request. It will be ready when the merge pull request button is green.
1717

18-
![screenshot of green merge pull request button](../../images/Green-merge-pull-request.png)
18+
![screenshot of green merge pull request button](/images/Green-merge-pull-request.png)
1919

2020
### :keyboard: Activity: Merge the pull request
2121

2222
1. Click **Merge pull request**.
2323
2. Click **Confirm merge**.
2424
3. Once your branch has been merged, you don't need it anymore. To delete this branch, click **Delete branch**.
2525

26-
![screenshot showing delete branch button](../../images/delete-branch.png)
26+
![screenshot showing delete branch button](/images/delete-branch.png)
2727

2828
4. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
2929

0 commit comments

Comments
 (0)