Repository navigation
Point repo references at stfc/goldilocks-agent - #25
Merged
Merged
Conversation
junwen94/goldilocks-agent was deleted and re-forked from this repository. Before that it was private, so its links were 404 for everyone but the owner, and its ghcr image couldn't be pulled anonymously. - The web app's "GitHub Issues" link now opens stfc/goldilocks-agent issues. - The local docker-compose.yml defaults to ghcr.io/stfc/goldilocks-agent, which is public. A fork can still override the owner with GOLDILOCKS_AGENT_IMAGE_OWNER. - AGENTS.md, README, docs, mkdocs repo_url and workflow comments are updated. References to the deleted issue #1 now point to design doc §13. Two dated historical notes in the design and plan docs are left as written. Closes #12
…mmits The "#3/#4/#5/#6/#7/#9" comments and README's "see issue #1" referred to junwen94/goldilocks-agent, which was deleted. On this repository the same numbers are unrelated PRs (#1 is the Ollama-backend PR). The comments now name the commits that fixed those bugs (cc5f0dc, c7bfc57), whose messages name the original issues. Refs #12
# Conflicts: # README.md # app/src/App.tsx
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.
Closes #12.
junwen94/goldilocks-agentwas deleted on 2026-10-09 and re-forked from this repository. Before that it was private, so its links were 404 for everyone but the owner, and its ghcr image couldn't be pulled anonymously. Each commit stands on its own.Point repo references at stfc/goldilocks-agent (0e98af3)
docker-compose.ymldefaults toghcr.io/stfc/goldilocks-agent, which pulls anonymously; README already said so. A fork can still override the owner withGOLDILOCKS_AGENT_IMAGE_OWNER.deploy/stfc-cloud/builds its own image and is unaffected.docs/index.md,docs/getting-started.md,mkdocs.ymlrepo_urland thedocker-publish.ymlcomments now point here. References to the deleted repo's issue STFC cloud deployment: switch chat backend from vLLM to Ollama #1 now point to design doc §13.Replace bare issue numbers from the deleted repo with their fixing commits (d1d1116)
App.tsxandgraph.pycited Split STFC cloud frontend build into public and internal variants #3–STFC cloud: disable Ollama's idle-unload so the model stays resident #7 and Bump urllib3 from 2.7.0 to 2.8.0 #9, and README said "see issue STFC cloud deployment: switch chat backend from vLLM to Ollama #1". Those were junwen94 issues; here the same numbers are unrelated PRs. The comments now name the commits that fixed those bugs (cc5f0dc, c7bfc57), whose messages name the original issues.Left as written on purpose: the dated CI entry in the implementation plan and the "v2 现状（2026-09-17）" snapshot in the ecosystem design doc. They describe the state on those dates. References to other junwen94 repos (
goldilocks-core,goldilocks-web) are out of scope.Testing
git grep junwen94/goldilocks-agentfinds only the two dated notes above.docker compose config --imagesgivesghcr.io/stfc/goldilocks-agent:latest.uv run poe check: 64 passed, 8 skipped.uv run poe web-checkis clean.Deploying: the issues link is compiled into the frontend, so the web version only picks it up after the image is rebuilt on the VM.