chore(stlc): seal custom-code tracking files - #4
Open
ladyofcode wants to merge 1 commit into
Open
Conversation
ladyofcode
force-pushed
the
stlc/seal-tracking
branch
4 times, most recently
from
August 27, 2026 01:16
847d7d4 to
284f0b4
Compare
ladyofcode
force-pushed
the
stlc/seal-tracking
branch
from
August 27, 2026 09:03
284f0b4 to
870f726
Compare
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.
Automated by the stlc generate workflow:
stlc buildre-sealed custom code (after a spec change onmain, or after absorbing custom code that landed on a staging repo out of band), updating the tracking files understainless/custom-code/. Merging brings the config repo in sync with the SDK repos. Safe to merge — tracking-files-only commits are skipped by this workflow, so it won't trigger another build.