uptodate
Sign in
Review

You review a pull request.

Nothing about your published docs changes on its own. Every fix uptodate drafts opens a branch and a pull request against your docs, and it waits there until you decide.

Update the session lifetime on the Authentication page

uptodate/session-lifetime into main

  • Docs site builds without errors
  • Every internal link still resolves
  • One reviewer approved the change
MKYou have the final say on this diff
Merge pull request

A human merge is the only thing that ships a change.

uptodate can open the pull request and lay out the reasoning, but it never touches your live docs. You read the diff, you merge, and only then does anything reach your readers.

Merge, and your published site catches up.

Because platforms like GitBook, Mintlify, and ReadMe build from git, the merge that closes the pull request is the same one that updates your live documentation. There is no separate publish step to remember.