openssl/openssl

CHANGES.md checks in CI are insufficient for the desired level of pedantry

Open

#31,306 opened on May 27, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C (11,262 forks)batch import
help wantedtriaged: feature

Repository metrics

Stars
 (30,157 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The checks for CHANGES.md in CI do not catch basic formatting pedantry that appears to be desired.

For example, some folks care about the number of leading spaces in a CHANGES.md file.

As none of these requirements are actually documented anywhere, the CHANGES.md checks in ci should catch these things so that they can be fixed not by wasting the limited processing power of meatspace entities on mindless pedantry better done by a computer.

Contributor guide

Research direction
Inspect the existing CHANGES.md validation in CI and add a new check to enforce consistent formatting (e.g., leading spaces).
Tech stack
c
Domain
documentationci cd
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gitbasic CI understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65