Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give your portfolio a header #4

Merged
merged 4 commits into from
Dec 7, 2020
Merged

Give your portfolio a header #4

merged 4 commits into from
Dec 7, 2020

Conversation

github-learning-lab[bot]
Copy link
Contributor

@github-learning-lab github-learning-lab bot commented Dec 5, 2020

Step 3: Add headers

As you saw on your website, your portfolio doesn't have much content yet. We'll learn how to edit the file in this pull request to incorporate some Markdown headers.

You can see an example of a header at the top of this page! Just like in HTML, a header is a larger bit of text at the beginning of a section. There are six sizes.

Example

# This is an <h1> header, which is the largest
## This is an <h2> header
###### This is an <h6> header, which is the smallest

How it looks

This is an <h1> header, which is the largest

This is an <h2> header

This is an <h6> header, which is the smallest

In issues, pull requests, and comments, you can use the text formatting toolbar.

The toolbar isn't available everywhere. When you edit a file, you must type the # symbols manually.

⌨️ Activity: Edit your file with headers

  1. In this pull request, click the Files changed tab.
  2. In the upper right corner of the file view, click the small pencil ✏️ icon for the file titled _includes/01-name.md.
  3. On the Edit file tab, add a # before the content to make it an H1 Header. You can add more headers, using one to six # characters.
  4. Above your new content, click Preview changes.
  5. At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file.
  6. Click Commit changes.

Watch below for my response.


View rendered _includes/01-name.md
View rendered index.md

@vizipi
Copy link

vizipi bot commented Dec 5, 2020

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code.
This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

Reviewers with knowledge related to these changes

Match % Person Commit Count Common Files
100.00 % GitHub Teacher 1 2
50.00 % reedhhw 2 1

Potential missing files from this Pull request

No commonly committed files found with a 40% threashold


Committed file ranks

(click to expand)
  • 66.67%[index.md]
  • 83.33%[_includes/01-name.md]
  • @vizipi vizipi bot requested a review from reedhhw December 5, 2020 18:48
    @reedhhw reedhhw self-assigned this Dec 7, 2020
    @github-learning-lab
    Copy link
    Contributor Author

    Step 4: Merge your headers

    I see you've added at least one header, @reedhhw. You can continue working if you'd like, otherwise let's merge 📖 this pull request and move on with the course.

    ⌨️ Activity: Merge the Pull Request

    1. Click Merge pull request below.

    Watch below for my response!

    Restyle Give your portfolio a header
    @reedhhw reedhhw merged commit 4ede487 into main Dec 7, 2020
    @delete-merged-branch delete-merged-branch bot deleted the add-headers branch December 7, 2020 13:19
    @vizipi vizipi bot requested a review from reedhhw December 7, 2020 13:20
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    3 participants