Trailer-looking lines can cause the parsing to abort early

[apricote]

If a commit includes some lines that look like trailers but were not intended as ones, this can throw off the parsing. This causes later actual trailers to be ignored.

As far as I could tell the conventional commit spec does not specify that only actual trailers may look like trailers.

I tried to make the changes in machine.go.rl myself but did not get anywhere.

Reproduction

Example commit that causes problems:

feat: some thing (hz/fl!144)

Fixes #15                             <-- Intepreted as a footer/trailer

Lorem ipsum dolor sit amet

BREAKING CHANGE: Some explanation
Reviewed-by: XX <[email protected]>

I would expect the following ConventionalCommit for this:

commit := ConventionalCommit{
	Type:        "feat",
	Description: ""
	Scope:       nil,
	Exclamation: false,
	Body:       pointer.Pointer("Fixes #15\n\nLorem ipsum dolor sit amet"),
	Footers: map[string][]string{
		"breaking-change": []string{"Some explanation"},
		"reviewed-by":     []string{"XX <[email protected]>"},
        },
}

Test Case

func Example_fake_trailer() {
	i := []byte(`feat: some thing (hz/fl!144)

Fixes #15

Lorem ipsum dolor sit amet

BREAKING CHANGE: Some explanation
Reviewed-by: XX <[email protected]>`)
	m, e := NewMachine().Parse(i)
	output(m)
	fmt.Println(e)
	// Output:
	// (*conventionalcommits.ConventionalCommit)({
	//  Type: (string) (len=4) "feat",
	//  Description: (string) (len=22) "some thing (hz/fl!144)",
	//  Scope: (*string)(<nil>),
	//  Exclamation: (bool) false,
	//  Body: (*string)((len=37) "Fixes #15\n\nLorem ipsum dolor sit amet"),
	//  Footers: (map[string][]string) (len=2) {
	//   (string) (len=15) "breaking-change": ([]string) (len=1) {
	//    (string) (len=16) "Some explanation"
	//   },
	//   (string) (len=11) "reviewed-by": ([]string) (len=1) {
	//    (string) (len=19) "XX <[email protected]>"
	//   }
	//  },
	//  TypeConfig: (conventionalcommits.TypeConfig) 0
	// })
	// nil
}