ci: rename style_guide_path to additional_instructions_path#267
Merged
Conversation
Tracks the upstream rename in alexanderlhicks/lean-summary-workflow. The input semantics are unchanged for this fork — the new name better reflects that the file passed in can be any deployment-supplied instructions, not just a style guide. Merge ordering: the upstream lean-summary-workflow PR renaming the input must land before this PR. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
🤖 PR SummaryInfrastructure / CI: Renames Statistics
Lean Declarations
🎨 **Style Guide Adherence**All changes adhere to the style guide. 📄 **Per-File Summaries**
Last updated: 2026-05-19 15:38 UTC. |
🤖 AI ReviewNo Lean files were changed in this PR. |
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.
Tracks the upstream rename in alexanderlhicks/lean-summary-workflow. The input semantics are unchanged for this fork — the new name better reflects that the file passed in can be any deployment-supplied instructions, not just a style guide.
Merge ordering: the upstream lean-summary-workflow PR renaming the input must land before this PR.
Description
Briefly describe your changes, and link any issues if appropriate.
Fixes # (issue number)
Checklist
PORTING.mdas appropriateauthorssection of any appropriate filesGenerative AI Guidelines
AI assistance is permitted when making contributions to Iris-Lean, however, generative AI systems tend to produce code which takes a long time to review.
Please carefully review your code to ensure it meets the following standards.
havestatements that do not aid readability or code reuse should be inlined.In our experience, a good place to begin refactoring is by re-arranging and combining independent tactic invocations.
We also find that pointing generative AI systems to the Mathlib code style guidelines can help them perform some of this refactoring work.