[WIP] Update documentation for git migration#240
Conversation
This change updates the documentation to account for the source code moving from Mercurial to Git. Closes thunderbird#239
|
@hellsworth What would be the best way to handle review/landing of these changes? Would it be easier, for all pages that are updated, to create a new page for git and keep the old one for mercurial? For example, we could have a page named "Hello World Example (Mercurial)" followed by a page named "Hello World Example (Git)". A bit more work on my end, but that would allow us to review/land this earlier rather than having to time it with the day/week we switch over to Git. Another thought, I've made several updates to switch searchfox URLs to GitHub URLs. I could remove those changes, or split them into a different commit. I'm not sure how desirable those changes will be. Having a separate commit would allow them to be reverted more easily if need be. |
1 participant
This change updates the documentation to account for the source code moving from Mercurial to Git.
The following sections still need updating:
./mach trythunderbird-development/fixing-a-bug/try-server.mdCloses #239