Clean up docs for fork maintenance
Leaving context for Future Amy: doc/user/project/repository/forking_workflow.md
has a section, With repository mirroring, that I intentionally left as a bit of a stub. I should revisit that subheading, because
- it contains a warning about syncing that I … have no idea what it refers to.
- more info may be harvestable from
Set the stage for work I'm likely to see in upcoming milestones from groupsource code to auto-update forks. We'll have new messaging that describes problems a fork can have, and troubleshooting info would be good.
The following discussion from !109250 (merged) should be addressed:
-
@aqualls started a discussion: (+3 comments) This section is incomplete still - it points to the blog post - in the interest of getting a MVC together in time for Docs Hackathon Jan 2023 planning issue (technical-writing#740 - closed). I think it's reasonable to assume that most folks participating in the Hackathon won't be in paid tiers (maybe I'm wrong here?) and I'm focusing my MVC effort on the method that's available to all users regardless of tier.
I need to review that 2016 blog post to see if there's anything else valuable in it, and figure out how to resolve this warning box. Should be done in a follow-up.
Technical debt, yay.
Related issues
- This issue is a follow-up to the MVC of Explain how to update a fork (!109250 - merged)
- Related to Docs Hackathon Jan 2023 planning issue (technical-writing#740 - closed) because that's how I found this gap
- Related to Fetch new upstream contents when fork is behind (#330243 - closed) because that work will trigger more docs work for this page