# lost notebook

**URL:** <https://talk.observablehq.com/t/lost-notebook/1208>\
**Category:** Help\
**Created:** [September 13, 2018, 7:53am UTC](https://talk.observablehq.com/t/lost-notebook/1208 "2018-09-13T07:53:22Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![RandomFractals](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/randomfractals/32/759_2.png) [@RandomFractals](https://talk.observablehq.com/u/RandomFractals)\
**Post date:** [September 15, 2018, 12:32pm UTC](https://talk.observablehq.com/t/lost-notebook/1208/7 "2018-09-15T12:32:00Z")

</div>

thanks for sharing this insight on how forks are managed by Observable.

do you think it would also be beneficial to have this feature related to forks and notebook updates?

> [@Feature request: Publish commit comments](https://talk.observablehq.com/t/feature-request-publish-commit-comments/1117):
>
> Since you are using slugs and version notebooks as they are published and refined, the one feature I found lacking is Publish comments for the updated notebook log tracking. Recently I just pulled down all my notebooks and put them in github repos, but I find myself doing it frequently with every major notebook update to keep track of what changed despite the fact that you can reference diff. notebook versions on observablehq. So, I propose adding an optional Note input box to the Publish butt…

---

_[View the full topic](https://talk.observablehq.com/t/lost-notebook/1208)._