2024-04-07, 03:13 PM
(This post was last modified: 2024-04-07, 03:15 PM by Efficient_Good_5784. Edited 1 time in total.)
Forking and cloning is the same thing. GitHub just uses the term fork to describe cloning.
Just in case there's a misunderstanding here, working on a clone means your work stays on your clone of the code base. Pull requesting means your work will be reviewed before it gets accepted to the actual code base. All this is to avoid conflicts of multiple people working on the same file(s) and causing issues with each other's code.
Just imagine you finished your bug fix, but another person pushed their own change before you did that resulted in your bug fix needing to be reworked again. It would be a mess directly pushing both to main before a review could be done.
Also since it wasn't brought up yet, yes there's a code freeze right now for 10.9. Non-bug-fix pull requests won't be accepted until 10.9 drops.
You can still submit pull requests, but they'll just sit there until the code freeze ends.
Just in case there's a misunderstanding here, working on a clone means your work stays on your clone of the code base. Pull requesting means your work will be reviewed before it gets accepted to the actual code base. All this is to avoid conflicts of multiple people working on the same file(s) and causing issues with each other's code.
Just imagine you finished your bug fix, but another person pushed their own change before you did that resulted in your bug fix needing to be reworked again. It would be a mess directly pushing both to main before a review could be done.
Also since it wasn't brought up yet, yes there's a code freeze right now for 10.9. Non-bug-fix pull requests won't be accepted until 10.9 drops.
You can still submit pull requests, but they'll just sit there until the code freeze ends.