Issue bodies and comments go through mdformat with the repository
configuration, so they wrap and number lists as every other Markdown
file does. mdformat joins trailer lines into one line, so the text is
formatted first and the trailers are added after it.
imperative mood, with no final period.
- Write the body in Markdown. State the result for the user, the scope,
and how to check it.
imperative mood, with no final period.
- Write the body in Markdown. State the result for the user, the scope,
and how to check it.
+- Format each body and comment with `mdformat -` in the repository, so
+ that it uses `.mdformat.toml`. mdformat joins trailer lines into one
+ line, so format the text first and add the trailers after it.
- Add a comment with `git bug bug comment new ID -m TEXT` for progress
that matters: decisions made with the user, measurements, and checks
that could not run.
- Add a comment with `git bug bug comment new ID -m TEXT` for progress
that matters: decisions made with the user, measurements, and checks
that could not run.
This example creates an issue:
```sh
This example creates an issue:
```sh
+body=$(mdformat - < body.md)
git bug bug new --non-interactive -t 'Decide the root wake interval' \
git bug bug new --non-interactive -t 'Decide the root wake interval' \
+ -m "$body
+
+Parent: 180a674"