Markdown Formatting Standardization Guide
@mbifeld is already working on this.
Since Oct 3, 2023.
Assessment
This issue has not been assessed yet.
Description
A lot of scenarios follow different practices for naming, variable declaration, comments, etc.
We need to create a standardization doc that scenario creators can follow as they format their md scripts.
- Dominant language
- Go
- Stars
- 40
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/InnovationEngine
-
Azure/InnovationEngine#262 · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/InnovationEngine#259 ·
-
bug enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure/InnovationEngine#258 ·
-
enhancement innovation engine
Azure/InnovationEngine#256 · 1 reaction · 1 assignee ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
Azure/InnovationEngine#252 · 1 comment ·
All issues in Azure/InnovationEngine
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day