Move explainers to their own subdirectory #98
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
Collaborator
Author
|
@svendlarsen PTAL and let me know your thoughts, especially since this affects where you might publish an explainer |
Contributor
|
I think an explainers directory makes sense. I think having the stateless BTM explainer here is also good — definitely improves discoverability vs. the current state of only having it in the comments of an issue. A symlink seems fine to me, though I'm still pretty new to spec/CG work so I'm not sure if symlinks are discouraged for some reason. If this PR changes to not symlink, then the link to the explainer from the spec should also be changed. |
svendlarsen
approved these changes
Mar 7, 2025
github-actions bot
added a commit
that referenced
this pull request
Mar 13, 2025
SHA: 15a4abf Reason: push, by MrPickles Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
Since there are additional explainers expected to be published around bounce tracking mitigations, this PR creates an
explainers/directory to hold all relevant explainers. Additionally, it puts the explainer for stateless BTM from #41 in the repository.The original BTM explainer at the top level is turned into a symlink to avoid creating a dead link. (However, I'm open to suggestions around this. Maybe it's better to just move the file without keeping a symlink and retroactively fix any incoming links from ChromeStatus or TAG reviews.)
Preview | Diff