Stop extension status polling when a status is resolved
Committed by AndrewBastin
feat: stop extension status polling when a status is resolvedEditor assessment
The subject is unusually specific for this size of message — it states the trigger ('when a status is resolved') and the action ('stop extension status polling'), which makes it genuinely useful in git log. It is imperative, lowercase, period-free, and at about 58 characters it stays within the 72-character comfort zone. Whether feat is the right type is debatable: stopping redundant polling reads more like a perf or refactor improvement than a new capability, and labeling it feat will inflate a minor version bump for something users may not perceive as a feature. A short body explaining the resource cost of the polling would have justified the choice. Coherent and spec-valid; the type boundary is the only real quibble.