# Notebook pull requests

**URL:** <https://talk.observablehq.com/t/notebook-pull-requests/492>\
**Category:** Feedback\
**Created:** [March 12, 2018, 4:01pm UTC](https://talk.observablehq.com/t/notebook-pull-requests/492 "2018-03-12T16:01:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![argyleink](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/argyleink/32/298_2.png) [@argyleink](https://talk.observablehq.com/u/argyleink)\
**Post date:** [March 12, 2018, 4:01pm UTC](https://talk.observablehq.com/t/notebook-pull-requests/492/1 "2018-03-12T16:01:48Z")

</div>

Would be really neat if a forked notebook could propose changes back upstream to the source notebook. Maybe this is even how collaboration is added to the platform? But code edits, copy edits, etc are all valuable PR’s that an author would probably happily review and accept. Thoughts?

---

<div class="post-metadata">

**Author:** ![jacobjensen](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/jacobjensen/32/187_2.png) [@jacobjensen](https://talk.observablehq.com/u/jacobjensen)\
**Post date:** [March 12, 2018, 4:40pm UTC](https://talk.observablehq.com/t/notebook-pull-requests/492/2 "2018-03-12T16:40:08Z")

</div>

Agreed. More than that though, a git(hub)-compatible notebook representation would be terrific on multiple levels. .ipynbs are text representation of jupyter notebooks and make them diffable and version controllable, Observable would thrive with the same.
