| Age | Commit message (Collapse) | Author | Lines |
|
|
|
A robustness test asked for the inner tag's page by id, but nothing
checked that the outer tag's page links there.
|
|
|
|
The tag requests passed on any answer short of a crash, and the title
test read a page the cache kept from an earlier test. The id pattern
also matched an empty id, the date row was checked only for its
opening tag, and the lightweight tag was never shown to lack a date
row. Two tests read a page an earlier test wrote.
|
|
The check removed every newline before matching, so a body that kept
the blank line after the subject read the same, and the page would
have shown that line under white-space pre-wrap.
|
|
The download row was already matched on the same tag page, no fold can
sit between the message and the signature the check requires, and the
submodule row is the one the test before extracted.
|
|
Summary, about, log, refs, tag and stats pages shared one title, so
tabs, history and search results could not tell them apart. Titles now
read page, repository and site, with root-title as the site, and the
description stays in the meta description, where search engines read
it.
|
|
The fold put a click between the reader and the signature, and the
browser's own disclosure marker and summary did not take the theme. The
signature prints as part of the message again, as it did up to v2.9.1.
|
|
The armour ran on for more lines than most tag messages, as part of the
message itself. git finds the signature for every kind it can sign
with, so PGP, SSH and X.509 all fold the same way.
|
|
The tag page offered a download for a tag of a tree or a blob, which
only led to a "Not a commit" page. The refs listing already checks.
|
|
|
|
|
|
|