Skip to content

Consider formatting markdown according to pre-commit expectations #16852

@LeonarddeR

Description

@LeonarddeR

cc @seanbudd

Is your feature request related to a problem? Please describe.

With the current pre-commit config, commits including changes.md will perform a major rewrite of the file due to trailing whitespace

Describe the solution you'd like

Format the docs according to pre-commit expectations.

Describe alternatives you've considered

  1. Exclude docs from pre-commit
  2. Disable pre-commit on merge. It seems almost impossible to perform a merge with conflicts without pre-commit kicking in

Metadata

Metadata

Assignees

No one assigned

    Labels

    audience/nvda-devPR or issue is relevant to NVDA / Add-on developersp4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions