Skip to content
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
This repository was archived by the owner on Nov 18, 2021. It is now read-only.

Leading zeroes should invalidate issue references #372

@stuartpb

Description

@stuartpb

When writing a number preceded by an octothorpe in an issue, pull request, or commit message, the number is parsed and interpreted as a reference to an issue number. This causes problems when the number refers to something else, such as a CSS color - particularly if the color has no red and a low green value, as GitHub interprets a color like #1138 as a reference to "Issue #1138" if such an issue exists. (See github-linguist/linguist#2269 for an example of a commit that encounters this issue, where the color #000080 is replaced with a linked "#80".)

Not interpreting any number after '#' that starts with a zero would generally fix colors being misinterpreted as issue references, as that would leave only values of #100000 and up to be possibly interpreted as an issue, and very few projects (none, to my knowledge) have a hundred thousand issues.

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