Skip to content

Inherited title not shown if description present #18

@tcharding

Description

@tcharding

Multiple patches which all inherit title gives:

============================================

## Development

Internal development changes

* Add tfile

* Check for changes to the public API

* Make commits conform to mkchlog format

============================================

If we change the second patch to use description: the title gets dropped

============================================

## Development

Internal development changes

* Add tfile

Generate the full public API as a set of text files and commit them to the repository, for each subsequent PR do the same and check that the final state of the pubic API is not different. Implies that changing the public API requires a patch to the committed API text files.

* Make commits conform to mkchlog format

============================================

And if we add a title then we get a new subsection which breaks the list

============================================

## Development

Internal development changes

* Add tfile

### Check for changes to public API in CI

Generate the full public API as a set of text files and commit them to the repository, for each subsequent PR do the same and check that the final state of the pubic API is not different. Implies that changing the public API requires a patch to the committed API text files.

* Make commits conform to mkchlog format

============================================

Expected behaviour

I was expecting to be able to inherit the title and get

============================================

## Development

Internal development changes

* Add tfile

* Check for changes to public API

   Generate the full public API as a set of text files and commit them to the repository, for each subsequent PR do the same and check that the final state of the pubic API is not different. Implies that changing the public API requires a patch to the committed API text files.

* Make commits conform to mkchlog format

============================================

or use a new title and get it as part of the list

============================================

## Development

Internal development changes

* Add tfile

* Check for changes to public API in CI

   Generate the full public API as a set of text files and commit them to the repository, for each subsequent PR do the same and check that the final state of the pubic API is not different. Implies that changing the public API requires a patch to the committed API text files.

* Make commits conform to mkchlog format

============================================

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions