# best practices for version control/branching/feature development? **URL:** \ **Category:** Help\ **Created:** [June 25, 2020, 4:19pm UTC](https://talk.observablehq.com/t/best-practices-for-version-control-branching-feature-development/3508 "2020-06-25T16:19:46Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![mootari](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mootari/32/581_2.png) [@mootari](https://talk.observablehq.com/u/mootari)\ **Post date:** [July 21, 2020, 7:45pm UTC](https://talk.observablehq.com/t/best-practices-for-version-control-branching-feature-development/3508/10 "2020-07-21T19:45:01Z")
> [@stephanietuerk](#): > > I wind up hand copy-pasting changes from one notebook (fork) into another (parent) now Please note that you can merge any notebook into any other notebook, regardless of their relationship (or parent author). See this comment for the detailed steps: > [@Feature Request: Allow the Removal of Fork Inheritance](https://talk.observablehq.com/t/feature-request-allow-the-removal-of-fork-inheritance/3208/3): > > You can already copy a notebook without creating a fork, because any two notebooks [can be merged](https://talk.observablehq.com/t/fork-multiple-notebooks/2004/2). The steps are not intuitive, so bear with me: Open the notebook that you want to copy. This is the ORIGINAL. Access the notebook ID: for private or shared notebooks: The part in the URL after “/d/”. for published notebooks: Access the notebook history; the ID is the part of the URL between “/d/” and “@”. Create a new notebook, save the first cell. This is the COPY. Open the URL https://observab… --- _[View the full topic](https://talk.observablehq.com/t/best-practices-for-version-control-branching-feature-development/3508)._