Skip to content

Conversation

@benjaminleonard
Copy link
Collaborator

Doesn't quite fix #181, since it's the processed and combined document, but that seems perhaps like a niche use case and we can't get that from the API.

@sunshowers is this useful? Not sure how you'd auth for non-public RFDs from an agent or CLI.

@vercel
Copy link

vercel bot commented Dec 22, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
rfd-site Ready Ready Preview Dec 22, 2025 10:21pm

@sunshowers
Copy link

Thanks -- happy to treat the private RFD use case separately. It would be nice to extend the RFD API to output documents before pre-processing, though -- having parts of the document live in another file has been pretty important for reducing the amount of context fed into the LLM.

@sunshowers
Copy link

(I also don't know whether it's okay to do this for all public RFDs, or just an allowlisted subset.)

@benjaminleonard
Copy link
Collaborator Author

If you ran the site in local mode, I think you might be able to view any RFD without logging in (don't quote me on that one).

@augustuswm
Copy link
Contributor

I think it is fine to make this available for all public RFDs. The fact we don't provide the exact files is just a detail of how the API is constructed.

The implementation of individual file access is definitely something we should implement in the API. The underpinning work that is needed is also needed for implementing more precise dependency change tracking, and something I have wanted to add for quite a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish raw .adoc files at well-known URLs

4 participants