There are a lot of changes since the last documentation on github-pages release.

For example:

And
<img width="686" alt="2017-02-11 0 28 40" src="https://cloud.githubusercontent.com/assets/4660275/22844844/1e1a394c-eff1-11e6-9124-4804d480b674.p

If I set my nbdime_config.json to:

{
  "Global": {
    "Ignore": {
      "/cells/*/execution_count": false
    },
    "details": false
  }
}

I expect the details and Ignore to be applied to every nbdime tool, given that

Global Options to apply to all commands.
[sections](https://github.com/jupyter/nbdime/blob/d44e3b5d09ba16163d71ef38e98f288c0a88b391/docs/

The docs mention "sbt-release has built in support to commit/push to Git, Mercurial and Subversion repositories." but does it really support SVN?
If so, can you provide examples on how to do this (instead of the default commit-t-git examples?)

I would really appreciate seeing this limitation documented a little further.

Specifically I would like to understand the issue with merge commits and know if there is a migration path from a codebase with a long history of these to one which would be ready to use fbshipit.

It would be a nice usability improvement if, upon cloning a repository, git-cinnabar autogenerated .git/info/exclude (or offered an option to do so) from .hgignore, at least in the case where .hgignore uses syntax: glob (which should be straightforward to convert to a .gitignore).

Maintaining two separate repos doesn't make sense.

I'm making changes to the code and the respective documentation together all the time, and this would be much easier if it just was in the same branch of the same repo.

Read the Docs also supports getting the documentation from a doc subdir in the main repo.

I’m not sure these files should be shown in the green color.

As seen with questions like #223, these source services are complex enough that we need proper docs for users, not just a README and some .service XML files.

• decide location of docs
• decide format of docs
• broken link to obscpio delta store in README (Issue #193)
• [add example of extract parameter](https:/

We should have pages in the BitBucket archive for branches, that include a link to the relevant GitHub repository branch page.