Skip to content

Feature/markdown as master #48

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

Merged
merged 17 commits into from
Jun 24, 2020
Merged

Feature/markdown as master #48

merged 17 commits into from
Jun 24, 2020

Conversation

ShMcK
Copy link
Member

@ShMcK ShMcK commented Jun 21, 2020

closes #40.

Treats the markdown as the source of truth. This means if a level/step isn't in the config, it will still build.

Allows for the new recommended way of labelling levels/steps:

In markdown:

  • Level: ## 1. Level one
  • Step: ### 1.1 A Label (label is optional)

And in commits:

  • 1 Level
  • 1.1 First step commit
  • 1.1S First step solution

@ShMcK ShMcK merged commit e4f5c19 into master Jun 24, 2020
@ShMcK ShMcK deleted the feature/markdown-as-master branch June 24, 2020 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use Markdown as master
1 participant