Repository navigation
docs(files): explain ownership and require_managed_files migration - #3201
Draft
shrey-berri wants to merge 2 commits into
Draft
shrey-berri wants to merge 2 commits into
shrey-berri wants to merge 2 commits into
Conversation
Contributor
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 of 6 tasks
This branch was successfully deployed
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.
what to review
Explain who can access uploaded files and how to migrate existing files before enforcing managed IDs
summary
decisions
Summary
require_managed_files: falserecords ownership for new plain-provider and model-routed uploads while preserving their IDs. Non-admin lists show files owned by the caller's user or team, but known untracked raw IDs still pass throughrequire_managed_files: truerequirestarget_model_namesand rejects raw provider IDs for admins and non-admins. The migration example re-uploads the source file and uses the returned unified ID. The config reference links to the updated sectionValidated with
npm run buildandpython3 scripts/check-docs.py(1,046 Markdown files, no structural problems). The final prose and anchor edits passed the structural check againDetails
Link to Devin session: https://app.devin.ai/sessions/a4a39d1173934993a004a733af3ca06c
Open in Devin Desktop: https://app.devin.ai/desktop/session/a4a39d1173934993a004a733af3ca06c?variant=devin
Requested by: @shrey-berri