Skip to content

Conversation

@evantahler
Copy link
Contributor

Rather than wait until the end of the week, we can run the generation of LLMs.txt on every PR, looking only for what has changed. Changes will be auto-commited back to your PR

@vercel
Copy link

vercel bot commented Nov 4, 2025

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

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Nov 4, 2025 10:39pm

@evantahler evantahler force-pushed the llms-txt-since-last-time branch from 7b5af51 to c960b1b Compare November 4, 2025 21:50
@evantahler evantahler marked this pull request as ready for review November 4, 2025 21:55
@evantahler
Copy link
Contributor Author

@sdserranog and @torresmateo what do you think about this pattern?

@torresmateo
Copy link
Collaborator

I like this pattern! I like opened and reopened for sure, but I'm not so sure about synchronize, as it may become too verbose when there's a lot of back and forth in a PR. But I'm willing to try!

@evantahler
Copy link
Contributor Author

I like this pattern! I like opened and reopened for sure, but I'm not so sure about synchronize, as it may become too verbose when there's a lot of back and forth in a PR. But I'm willing to try!

Yeah, but what I was worried about was the page content changing, and the summary being inaccurate.

Copy link
Collaborator

@torresmateo torresmateo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

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.

3 participants