Repository navigation
Fix misleading Build Watch time counters - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build Watch displayed the age of GitHub's last update as a ticking counter, so completed pipelines appeared to keep running. Rows now show a fixed, explicitly labeled update date and 24-hour time, with the full timestamp in the tooltip and accessibility label.
Update the README and sample screenshot to explain the timestamp and the existing polling delay, and bump Broschy to 0.8.1.
Validation: the local release build, property-list validation, and code-signature verification passed. Manual checks against this repository confirmed completed runs show Passed and retain their timestamps after Refresh. The sample layout was also checked for truncation. CI runs the existing isolated checks and release-bundle verification.