Repository navigation
Align public docs and dynamic methodology release checks - #99
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.
What changed
The contribution instructions named a private tracker that the public-surface policy disallows. They now offer public pull requests and the support email; an internal tracking reference in the PDF validator is also removed. The README keeps contributor build and publication verification steps while dropping hosting history, runner details and fixed inventory counts.
The methodology page now defaults to GitHub's latest-release URL, so it remains useful without JavaScript or when the API is unavailable. CI executes the page's release-loading code with controlled responses instead of requiring a committed version tag to match a live API response. Tests cover future releases, unavailable or malformed responses, invalid release metadata and URL encoding. The workflow runs when the page, tests or workflow changes; the new test is declared as repository-only.
How it is verified
GitHub Actions at
f9bf44e: all 13 checks pass, including CodeQL and the release-loading tests. The auto-merge job is skipped.The consumer artifact excludes the README, contributor scripts, workflows and new test. Publication remains a separate manual operation.