avanderhoorn Semantic-Release-Notes issues

avanderhoorn / Semantic-Release-Notes

Retrieving typed Release Note information from a Markdown based syntax

30 stars 4 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Readme Rules

#23 avanderhoorn opened 2 years ago
0
Readme Rules

#22 avanderhoorn closed 2 years ago
0
Update README.md

#21 avanderhoorn closed 2 years ago
0
Add tools section

#20 laedit closed 9 years ago
0
Support metadata

#19 laedit opened 9 years ago
8
Standardize rendering priorities

#18 laedit closed 9 years ago
1
Handle categories / Fix #4

#17 laedit closed 9 years ago
8
Can an Item have a multi-lines summary?

#16 laedit closed 8 years ago
3
Is there some tests available to check if a tool is valid to the spec?

#15 laedit opened 9 years ago
5
Include optional footer for commit range

#14 JakeGinnivan opened 10 years ago
25
Initial proof of concept for an F#/FParser-based parser of the Semantic-Release-Notes format.

#13 davidalpert opened 10 years ago
0
Fixed grammar

#12 flagbug closed 11 years ago
1
Provide a way to assign a date to each release

#11 flagbug opened 11 years ago
56
updated regex for section headers, fixes #1

#10 shiftkey closed 11 years ago
0
Make @shiftkey A Core Contributor

#9 nikmd23 closed 11 years ago
3
Version the Spec

#8 nikmd23 closed 11 years ago
1
Support for Semantic/Common Hypermedia?

#7 nikmd23 opened 11 years ago
9
Severity instead of Priority?

#6 shiftkey opened 11 years ago
18
Drop "Project" from spec

#5 shiftkey closed 11 years ago
2
Change "Category" to be more free-form

#4 shiftkey closed 9 years ago
15
Semantics - Release vs Version

#3 shiftkey closed 11 years ago
4
[Idea] Using plain text files as inputs to SRN

#2 shiftkey opened 11 years ago
7
Example Parser does not handle sections labels containing space

#1 shiftkey closed 11 years ago
1