aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/ProfileData/Coverage/CoverageMapping.cpp
diff options
context:
space:
mode:
authorAlex Bradbury <asb@igalia.com>2023-10-02 21:13:55 +0100
committerGitHub <noreply@github.com>2023-10-02 21:13:55 +0100
commit3dda1040d3fe56dbd8afd2eb823e891954de13f3 (patch)
treebcc5a91ddbe60203fd2d41d00093d8fa6952de90 /llvm/lib/ProfileData/Coverage/CoverageMapping.cpp
parent3c0990c188e97086dec70ce1a36729f236f86093 (diff)
downloadllvm-3dda1040d3fe56dbd8afd2eb823e891954de13f3.zip
llvm-3dda1040d3fe56dbd8afd2eb823e891954de13f3.tar.gz
llvm-3dda1040d3fe56dbd8afd2eb823e891954de13f3.tar.bz2
[docs] Advise contributors to check for truncated PR titles (#68021)
GitHub will use the first line of the commit as the title for a single-commit PR, but truncates it at 72 characters <https://github.com/orgs/community/discussions/12450>. This truncation makes the PRs less readable if not manually undone, and even worse, the truncated form may survive through to commit if "Squash and rebase" is used in the GitHub web UI. From preparing LLVM Weekly, I've seen this a number of times and it really does make it more annoying to flick through commits. I'm not sure if this is the best place for the guidance, or whether you get the same behaviour when creating a PR with `gh`, but I'm quite keen we give a warning of some sort about this behaviour.
Diffstat (limited to 'llvm/lib/ProfileData/Coverage/CoverageMapping.cpp')
0 files changed, 0 insertions, 0 deletions