test: exercise tessl-lint workflow (do not merge)#107
Closed
test: exercise tessl-lint workflow (do not merge)#107
Conversation
Runs tessl skill lint on every PR and push to main, scoped to changed tiles (parents of tile.json) following the same discovery pattern as tessl-eval.yml. Push to main lints all tiles. Fails CI on lint errors (non-zero exit). Lint warnings (orphan files, oversized SKILL.md, etc.) are surfaced as GitHub Annotations and step summary entries but do not fail the build, since they are informational not blocking. No TESSL_TOKEN required — lint is local validation, so it works on fork PRs unlike eval/review. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Promotes per-tile warning-count annotations from ::notice:: (blue ℹ️) to ::warning:: (yellow⚠️ ) so they're more visible in the PR Conversation tab and Files Changed tab. Still doesn't fail the check — GitHub has no "warning" check status, only success/failure/neutral. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds a trailing comment marker to page-import SKILL.md so the tessl-lint workflow (introduced in #106) sees a tile change and runs against the EDS tile in its current main-branch state (with all the warnings PR #104 will fix). Demonstrates how warnings surface in the GitHub UI. This PR will be closed without merging. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
shsteimer
force-pushed
the
test/exercise-lint-warnings
branch
from
c0fed65 to
d5d0550
Compare
Iterating on test branch to evaluate UX before porting to PR #106. Posts a sticky comment to the PR Conversation tab summarizing per-tile lint results. Comment is identified by an HTML marker and updated in-place across pushes (Codecov-style), so a PR has at most one tessl-lint comment regardless of push count. Per-tile warnings are shown inside collapsible <details> blocks so the comment stays compact at a glance. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Tessl Skill Lint
|
6 tasks
Collaborator
Author
|
Iteration complete — sticky-comment workflow change is now on PR #106. Closing without merging; the test commit on page-import/SKILL.md was for triggering the workflow only and isn't needed. |
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.
Purpose
Demonstrates the `tessl-lint` workflow (#106) running against the EDS tile in its current main-branch state — i.e. before #104 lands its cleanup. Shows how lint warnings appear in the GitHub UI.
Where to look
After the workflow runs, check:
Expected for the EDS tile (current main):
The job should still pass (warnings are informational, not errors).
Cleanup
This PR will be closed without merging once we've reviewed the workflow output.
🤖 Generated with Claude Code