Timeline for How to determine when to open a new branch or a new repository when using Git?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2019 at 10:50 | comment | added | jsaddwater | I ended up choosing the fork with upstream setup for my client projects. | |
| Oct 30, 2019 at 13:57 | comment | added | Shauna | That said, I think it's worth noting that the concept of "forks" is a value-add from Github, et al, and not a concept in git, itself. Understanding that distinction might make it easier to understand and suss out the relationships between the different code bases. Forks are really just clones with an "upstream" remote (which is also how you bring in changes from upstream). | |
| Oct 30, 2019 at 13:55 | comment | added | Shauna | Are you talking after things are extracted? Once things are extracted, they'd be added as a library, however your language handles that (ie - for PHP, you'd point to it in your composer.json file and bring it in with Composer; for JS you'd do the same in NPM/Yarn). If you haven't extracted yet, and can't bring the old system whole cloth in as a sort of temporary library until you extract things out, then you'd have to fork it. | |
| Oct 29, 2019 at 15:05 | comment | added | jsaddwater | So how do you start the "client repo" ? A fork ? How do you pull changes from the base repo ? | |
| Dec 30, 2015 at 16:19 | history | edited | Shauna | CC BY-SA 3.0 |
added explanation for repo fork vs branch
|
| Dec 30, 2015 at 16:08 | history | answered | Shauna | CC BY-SA 3.0 |