I asked this question in gitter yesterday but didn't see an answer. I hope that @githubteacher or one of the other helpers who I don't seem to be able to at mention (maybe they aren't collaborators? can give me a pointer.
I understand why we forked for the class. And I know the process will be different on every project. But can you give an overview or a pointer to typical workflow with forks. From the student manual, it says the use cases are if no write access and to control PRs, in cases where these do not apply do forks have any advantages? Do you have a pointer to the workflow for PR merge process?
Branches are short lived for the cycle of a unit of change, eg a bugfix. But does one keep their own fork for the whole contribution to a project? And merge into master but then continue working on the fork with a rebase like action? In my company's GHE I clicked on the number next to the fork button to see that forks exist, and see the network screen shows some activity, I am looking for general concepts before I query other teams for conventions.
(Unfortunately, I am starting the repos for my teams projects with a full set of newcomers, so I need to set the groundwork myself)
:fork_and_knife: no knife, just a fork :-)
I asked this question in gitter yesterday but didn't see an answer. I hope that @githubteacher or one of the other helpers who I don't seem to be able to at mention (maybe they aren't collaborators? can give me a pointer.
I understand why we forked for the class. And I know the process will be different on every project. But can you give an overview or a pointer to typical workflow with forks. From the student manual, it says the use cases are if no write access and to control PRs, in cases where these do not apply do forks have any advantages? Do you have a pointer to the workflow for PR merge process?
Branches are short lived for the cycle of a unit of change, eg a bugfix. But does one keep their own fork for the whole contribution to a project? And merge into master but then continue working on the fork with a rebase like action? In my company's GHE I clicked on the number next to the fork button to see that forks exist, and see the network screen shows some activity, I am looking for general concepts before I query other teams for conventions.
(Unfortunately, I am starting the repos for my teams projects with a full set of newcomers, so I need to set the groundwork myself)