Uh oh!
There was an error while loading. Please reload this page.
fix: checksum error with lipgloss - #151
Closed
gjtiquia wants to merge 1 commit into
Closed
Conversation
thdxr
commented
Jun 16, 2025
Member
appreciate it but i think i just fixed it? we'll see if CI finishes |
gjtiquia
commented
Jun 16, 2025
Author
sure! |
gjtiquia
commented
Jun 16, 2025
Author
https://github.com/sst/opencode/actions/runs/15691799228 yep the CI finishes👍 i'll close this PR then, cuz its literally the same fix haha keep up the good work! |
randomm referenced
this pull request
in randomm/opencode
Jan 9, 2026
* feat(#136): replace mypy with ty type checker in Python agent * docs: update AGENTS.md to use unified ruff formatting Remove redundant black references: - black --check → ruff format --check - ruff format && black → ruff format - Unified Astral tooling (ruff for lint+format, ty for types) * docs(#149-#154): add dual-config architecture context to epic and feature issues Adds comprehensive dual-config architecture guidance to Epic #149 and issues #150-#154: - Epic #149: Overview of dual-config requirement and graceful degradation principle - Issue #150: Job queue config for both, Shortcut integration (work-only) - Issue #151: Rules system (config-independent), testing on both configs - Issue #152: Hook system with work-only Shortcut hooks, configuration patterns - Issue #153: Memory compression identical on both, context preservation differences - Issue #154: Device registry with config_source tracking, cross-config validation Key principles documented: - Core feature parity across both configs - Graceful degradation for work-only integrations (Shortcut, Rollbar) - Config-independent core logic with permission differences - Mandatory testing on both opencode.work.json and opencode.personal.json Specialists implementing these features must: 1. Test on BOTH machine-specific configs 2. Verify graceful fallback on personal config 3. Track config_source in device registry schema 4. Preserve GitHub issue references in compression * fix(#156): enforce zero test failures across all language agents Add ZERO TEST FAILURES section to all 7 language architect prompts: - Python, Rust, Rails, Go, React Web, React Native, Shell Each section enforces: - ALL tests must pass (unit AND integration) - Prohibited rationalizations (pre-existing, external, flaky, unrelated) - Required protocol: STOP → REPORT to PM → WAIT - Output format must show failure count Prevents agents from rationalizing away test failures as "pre-existing" or "unrelated" while claiming quality gates passed.
randomm referenced
this pull request
in randomm/opencode
Jan 9, 2026
bussard76 pushed a commit
to bussard76/openwork
that referenced
this pull request
May 12, 2026
Add Tailwind v4 theme scaffolding
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
bun run src/index.tsgave me these errorsupdated the
go.sumrelated to #131