Repository navigation
docs(r-cran-status): verify win-builder submissions - #97
Merged
Merged
Conversation
Add a Win-Builder section that verifies whether a package submitted via check_win_devel() actually arrived on win-builder: FTP drop folder listing as the authoritative receipt check, the incoming_pretest/ listing for progress, and gotchas covering queue delays and lost results emails. Bump skill version to 1.0.1.
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.
Summary
Adds a Win-Builder section to the
r-cran-statusskill so agents can answer questions like "did win-builder get my package?" or "is win-builder processing my submission?" (both added as trigger phrases to the skill description).R CMD checkon Windows for packages submitted viacheck_win_devel()(or_release()/_oldrelease()); the tarball is uploaded by anonymous FTP to a per-flavor drop folder and results are emailed to the maintainer inDESCRIPTIONwithin ~15–30 minutes.incoming_pretest/web listing shows check progress — entry format{package}_{version}_{yyyymmdd}_{hhmmss}, with00check.loginside each entry. Entries linger for months, so match version and date, not just the name.check_win_devel()requests → Win-Builder section.Token budget
The description sits exactly at the 100-token limit from
count-skill-tokens.py; the body remains well under the 5,000-token / 500-line limits. An initial draft of the section was compacted by ~170 tokens during review without losing any guidance.