Repository navigation
Conversation
The Infisical CLI 0.44 migrates the per-machine project binding from .infisical.json to .infisical.yaml on first run. It is machine state like the old file, so it is ignored the same way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 57 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
…s roadmap-check Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
land-pr autopilot paused (label Remove the label to hand it back to the autopilot. |
|
Closed without merging: roadmap-check fails on Clearify's 46 open lines, all last confirmed 2026-09-10, and the unattended fixer re-dated every one of them without checking any. Re-confirming them just to land a one-line ignore rule would hide that the roadmap is stale. Clearify gets the ignore line once its roadmap is triaged (do, drop or genuinely re-confirm each line). |
What
Adds
.infisical.yamlto.gitignore, next to.infisical.json.The Infisical command-line tool (0.44) migrates the per-machine project binding from
.infisical.jsonto.infisical.yamlon its first run, and prints "commit it if this project is under version control". This binding stays machine state, never source, so the new file needs the same ignore line or the nextgit add -Acommits it. Seen first in claude-session-dashboard on 2026-10-20; the same line goes to every active repo that ignores.infisical.json.🤖 Generated with Claude Code
Summary by CodeRabbit