Contributing to Biopython.org via GitHub
Peter Cock <[email protected]>
| Newsgroups | gmane.comp.python.bio.devel |
|---|---|
| Message-ID | <CAKVJ-_7zy033wfW2sWTEJSuM6UgeubSZRfM9QWPcU55j=uJJhw@mail.gmail.com> |
On Fri, Apr 15, 2016 at 4:24 PM, Peter Cock <[email protected]> wrote: > > Hopefully we won't need to rewrite the git history again? > > If you want to fork this, rename the repository to your-username.github.io > e.g. My fork is at peterjc.github.org and can be viewed online at > http://peterjc.github.io > > Note you may get a warning email from GitHub pages saying the > CNAME has been ignored (peterjc.github.io can't use the CNAME > entry saying biopython.org because biopython.github.io already > has it). > > Regards, > > Peter > > There's several things we need to tweak listed here - please file more issues or pull requests: https://github.com/biopython/biopython.github.io/issues FYI: Here's one of the warnings I got while updating peterjc.github.io One way to side-step this might be to move all the biopython.org/wiki/ content to a GitHub Pages for a "wiki" project, much like how I moved all the biopython.org/DIST/ content to a "DIST" project: https://github.com/biopython/DIST That would need a little work dealing with the "wiki/" prefix, but is it worthwhile? Peter ---------- Forwarded message ---------- From: GitHub <[email protected]> Date: Fri, Apr 15, 2016 at 4:19 PM Subject: [peterjc/peterjc.github.io] Page build warning To: Peter Cock <[email protected]> The page build completed successfully, but returned the following warning: CNAME already taken: biopython.org. Check out https://help.github.com/articles/troubleshooting-custom-domains/#cname-already-taken for more information. GitHub Pages was recently upgraded to Jekyll 3.0. It may help to confirm you're using the correct dependencies: https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0 For information on troubleshooting Jekyll see: https://help.github.com/articles/troubleshooting-jekyll-builds If you have any questions you can contact us by replying to this email. _______________________________________________ Biopython-dev mailing list [email protected] http://mailman.open-bio.org/mailman/listinfo/biopython-dev