Sponsored by: Netflix
This section doesn't seem to document setting origins, unfortunately. I can see that you're reusing text from another section though, so probably a bit harsh to reject this on that basis - unless you want to fix that at the same time, I'll take a separate PR to fix that.
The content looks good to me, just some minor nits.
I'm wondering if we need to use "GitHub" instead of github...
have them be committed => have them committed?
Similarly, we should probably settle git vs Git across the doc.
setup => set up?
This line sounds a bit confusing to me from a reader's perspective - [what] can also work, without conflict [against what], when there are [?]. Perhaps breaking into two sentences and rephrasing it?
IMO the first comma is not needed
Also, should we avoid the word "merge" here? Since IMO it means continue/finish the rebase here.
We don't currently, and such a change would be beyond the scope of this change.
-> "and have them pushed into the FreeBSD's tree from there."
I tried to do that in the draft docs before we landed them into the tree, so I'll do this here.
Or omit it entirely.
Will give it a shot.
Do we need to/encourage reviewing the diff again after fast-forwarding? IMO it's fine 99.9% of the time but... (question mark)
Huh... What does this mean ;)
If we are closing the PR on the web interface anyways (as the above sentence stated), why does "requiring an account" depend on HTTPS or not?
You can do all the steps of fetching the changes, preparing them for commit and pushing them into the FreeBSD w/o a github account.
Is there a better way to say that?