| Attempt | #1 | #2 | #3 | #4 | #5 | #6 | #7 | #8 | #9 | #10 | #11 | #12 |
| :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
| Seconds | 301 | 283 | 290 | 286 | 289 | 285 | 287 | 287 | 272 | 276 | 269 | 254 |
Making your example shorter to make easier to understand.
| Attempt | #1 | #2 |
| :---: | :---: | :---: |
| Seconds | 301 | 283 |
And formatted to make it even easier to read.
| Attempt | #1 | #2 |
| :---: | :---: | :---: |
| Seconds | 301 | 283 |
Headers must be separated by pipe |
characters and underlined by -
dash characters. There must be at least three hyphens in each column.
You can create tables by assembling a list of words and dividing them with hyphens -
(for the first row), and then separating each column with a pipe |
.
First Header | Second Header
------------- | -------------
Content Cell | Content Cell
Content Cell | Content Cell
For aesthetic purposes, you can also add extra pipes on the ends:
| First Header | Second Header |
| ------------- | ------------- |
| Content Cell | Content Cell |
| Content Cell | Content Cell |
— GitHub Flavored Markdown
Our example becomes:
| Attempt | #1 | #2 |
| ------- | --- | --- |
| Seconds | 301 | 283 |
Finally, by including colons : within the header row, you can define text to be left-aligned, right-aligned, or center-aligned:
| Left-Aligned | Center Aligned | Right Aligned |
| :------------ |:---------------:| -----:|
| col 3 is | some wordy text | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |
— GitHub Flavored Markdown
So to center align, our example becomes:
| Attempt | #1 | #2 |
| :-----: | :---: | :---: |
| Seconds | 301 | 283 |
.md
files in a git repo., like theREADME.md
file. I migrated about 300.md
files from Azure DevOps Wiki and most all tables came across and render just fine. That’s without the "preceding blank line" and without the "required" 3 hyphens (dashes). The few tables that did not render correctly were due to the column header line specifying more columns than the table contained. Azure DevOps Wiki engine didn’t mind. GitHub’s rendering did. Finding the source of the issue was painful. Fixing it was trivial. – Tenpenny