fork

Currently, we have one LICENSES file in the repository that contains the license text for all 3 licenses that we use for the project. This is not ideal and is not machine-readable.

The FSFE REUSE Software website FAQ lists How to properly declare multi-licensing?.

You should

#197 took care of being able to use # at the start of a line, but I just noticed that there isn't a great user flow for editing an issue that already has markdown headings.

1. Create an issue with at least 1 heading
2. Edit the issue with lab issue edit [ID]
3. Make changes and save
4. The issue will now have its heading(s) stripped out

I'm not sure what the best course would be, but