Repository navigation
chore: correct the README and add repository metadata - #5
Merged
Merged
Conversation
…d the layout The full validation was described as taking about two hours; final-check.yml records 3 minutes for 962,384 records on 2026-10-31. The README also said no bot account is involved, which the final-check comment job contradicts. List every top-level piece in the layout and say how this repository relates to TechAPI.
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 & why
The README contradicted the workflows in two places: it gave a full validation run as about two hours, where the final check measures about three minutes for 962,384 records, and it said no bot token is used, although the final check posts one comment with
TECHENGINEBOT_TOKEN. Both are corrected, and the layout and the relation to TechAPI are written down.Changes
summary.json..github/CODEOWNERSand a pull request template, as the other satellite and the satellite template have.deploy-pages.yml: the deploy job gets a 10-minute timeout. Nothing else in the workflows changes..pytest_cache/..editorconfigand.gitattributes(* text=auto eol=lf). Every tracked file, data included, is already LF.No file under
data/changes.Checks
pytest: 11 passed locally.