docs: adopt two-step rename+translate commit structure in xtend-to-java skill#1453
Draft
joaodinissf wants to merge 1 commit into
Draft
docs: adopt two-step rename+translate commit structure in xtend-to-java skill#1453joaodinissf wants to merge 1 commit into
joaodinissf wants to merge 1 commit into
Conversation
…va skill Replace the single-commit rule with a rename -> translate structure: a pure git-mv commit (100% similarity, so git log --follow and blame permanently traverse the migration boundary) followed by an in-place translate commit (guaranteed side-by-side Xtend-vs-Java diff on the PR Commits tab), plus the existing infrastructure-cleanup commit when a module goes fully off Xtend. Documents the accepted trade-offs: the rename commit intentionally does not compile (one bisect-skip on master after rebase-merge), and the aggregate Files-changed tab pairing is unaffected by commit structure (it depends only on end-state content similarity). Co-Authored-By: Claude Opus 4.8 <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
1 participant
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
Replaces the xtend-to-java skill's single-commit rule with a two-step rename → translate structure (first applied in #1452):
git mvof the.xtendsources to.java, content unchanged. The 100%-similarity rename edge meansgit log --followandgit blamepermanently traverse the migration boundary (a combined delete+add only preserves history when the finished Java stays above Git's similarity threshold, which heavy rewrites don't).Documented trade-offs: the rename commit intentionally does not compile (one
git bisect skipon master after rebase-merge; PR CI builds only the head), and the aggregate Files-changed tab is unaffected by commit structure (its old/new pairing depends only on end-state content similarity).Touches:
formatting-and-commit.md(main rewrite),validation-checklist.mdrule 22,multi-file-batch.mdcommit section.🤖 Generated with Claude Code