STA-157: Attribute reports to explainers and publishers - #18
Merged
Conversation
A version 1 ExplainDocument now accepts an optional, strictly validated metadata object: explainedBy is authored in explanations.yaml, publish adds publishedBy from git config user.name, and the review service stamps its own publishedAt. Local views and exports show only the author, hosted reports show all three, and absent values are omitted without blocking any path. Co-Authored-By: ことね <kotone@claudecafe.dev>
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
2 participants
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.
User benefit
Reports can identify the self-reported explainer and publisher while preserving anonymous, account-free publishing. Hosted reports receive a service-generated publication time; local views and exports only show the explainer.
Verification
Scope
Closes STA-157