Commitc767cc6

committed

update readme to test publish

Signed-off-by: shmck <shawn.j.mckay@gmail.com>

1 parent2cf4e6f commitc767cc6Copy full SHA for c767cc6

File tree

-3

lines changed

-3

lines changed

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -104,19 +104,19 @@ commit 8e0e3a42ae565050181fdb68298114df21467a74 (HEAD -> v2, origin/v2)`
`104`	`104`	`Author:creator <author@email.com>`
`105`	`105`	`Date:Sun May 3 16:16:01 2020 -0700`
`106`	`106`
`107`		`-1.1setup for level 1, step 1`
	`107`	`+1.1some message`
`108`	`108`
`109`	`109`	`commit 9499611fc9b311040dcabaf2d98439fc0c356cc9`
`110`	`110`	`Author:creator <author@email.com>`
`111`	`111`	`Date:Sun May 3 16:13:37 2020 -0700`
`112`	`112`
`113`		`-1.1Ssolution for level 1, step 1`
	`113`	`+1.1Ssome message`
`114`	`114`
`115`	`115`	`commit c5c62041282579b495d3589b2eb1fdda2bcd7155`
`116`	`116`	`Author:creator <author@email.com>`
`117`	`117`	`Date:Sun May 3 16:11:42 2020 -0700`
`118`	`118`
`119`		`-1.2setup for level 1, step 2`
	`119`	`+1.2some message`
`120`	`120`	```
`121`	`121`
`122`	`122`	Note that the step`1.1` has two commits, one with the suffix `S`. The first commit refers to the required tests and setup, while the second optional commit contains the solution. If there are multiple commits for a level or step, they are captured in order.

Comments

(0)