Repository navigation
Add CLAUDE.md rules learned from recent issues - #511
Merged
Merged
Conversation
Branching/release flow, issue workflow, Az error handling, strict mode pitfalls and test conventions (tests first for bug fixes, Write-Error mocks, both ErrorActionPreference values, both publish methods). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds project rules to
CLAUDE.md, based on what we ran into while working on #404, #435 (#507, #508), #295 and the 1.19.0 release. No code changes.New sections
developand PRs intodevelop, never straight intomaster(Fix unit tests for Pester 6 and VS Code host #501 #502 was). Release viadevelop→master, then movedeveloptomaster. Version andModuleVersionare set at release; feature PRs use[Unreleased].Closes #nin PRs.-ErrorAction Stopinsidetry. Retry only temporary errors withInvoke-AdfWithRetry. Validation belongs inTest-AdfCode. A failed object deployment stops the publish; a failed trigger start/stop is a warning.$null.Countthrow;ifassignments unroll arrays.Added to existing sections
Write-Error, notthrow; run tests under bothStopandContinue; deployment tests cover both publish methods.🤖 Generated with Claude Code