Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
How to manage the "alternate" devguide branch for PEP 588? #519
Comments
|
I would expect that you maintain the github-issues branch as a branch of master, just like we do for branches of cpython master. Rather than 'backport' you occasionally merge upstream/master into github-issues. I don't know if you are using the fork workflow for other repositories or if people just push to python/whatever. One way to make a formatted (html) version of the alternate available to read would be to check it in, possible into a separate branch. I keep a trailing-whitespace-trimmed copy of idle.html in idlelib so that people can read it from the IDLE menu without being online. (The copy function is in idlelib/help.py.) Git has no problem with html. |
For PEP 588's purpose, we want to have an alternate branch of the devguide where the new workflow of using GitHub issues can be documented, and we want to have this branch ahead of the migration.
Sounds to me we will have to maintain two devguide branches:
masterbranch andgithub-issuesbranch.I don't remember anymore how this was done when we migrated the codebase from hg to GitHub.
The text was updated successfully, but these errors were encountered: