Repository navigation
feat: preserve WebGPT context in repository projects - #1
Merged
Merged
Conversation
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.
Summary
Repository-scoped WebGPT work now checks for an existing ChatGPT Project on first use, reuses or creates it through the coordinator, and starts tasks inside that Project. The shared skill documents source provenance, version handling, upload verification, and file limits.
Adds a local
project_context.pyCLI to look up and bind repository Projects and preserve Project/conversation URLs in task state. Conflicting bindings are rejected, and Forge refuses a PR from another repository before testing or publishing comments. Browser actions remain coordinator-driven.Validation
python3 -m pytest -q: 57 passed.git diff --check: passed.