Repository navigation
chore(core): sync method-core b202d7a (issue label from method identity) - #136
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.2 <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.
Syncs Method Core at
b202d7a(phense/method-core#1): the managed issue label is read from the bundling method'smethod.jsoninstead of a fixed name. For this repository the label staysengineering-method, so behaviour is unchanged; the sync keeps the pinned core revision current.python3 scripts/sync-core --check— passed, 69 filespython3 scripts/validate-plugin— exit 0python3 -m unittest discover -s tests -t .— 340 tests OK🤖 Generated with Claude Code