From 6760976d0e1868a03196d90949dd619cff7f89d9 Mon Sep 17 00:00:00 2001 From: Sean Hammond Date: Wed, 10 Apr 2013 17:51:03 +0200 Subject: [PATCH] Fix broken link in CONTRIBUTING.rst There seems to be a bug in GitHub's restructured text rendering, an internal link to a section with a ' in its title will be broken (but it works fine in Sphinx). Rename the section to workaround this. --- CONTRIBUTING.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index e3d8c461661..5cbf062dd5a 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -7,7 +7,7 @@ Contributing to CKAN .. _docs.ckan.org: http://docs.ckan.org (This section is about contributing code, if you want to contribute -documentation see `Contributing to CKAN's Documentation`_.) +documentation see `Contributing to the CKAN Documentation`_.) CKAN is a free software project and code contributions are welcome. To contribute code to CKAN you should fork CKAN to your own GitHub account, push @@ -124,7 +124,7 @@ When submitting a pull request: `CHANGELOG file `_ briefly summarising your code changes. - Your branch should contain new or updated documentation for any new or - updated code, see `Contributing to CKAN's Documentation`_. + updated code, see `Contributing to the CKAN Documentation`_. - Your branch should be up to date with the master branch of the central CKAN repo, see `Keeping Up with master`_. - All the CKAN tests should pass on your branch, see @@ -139,9 +139,9 @@ When merging a feature or bug branch into master: - Use the ``--no-ff`` option in the ``git merge`` command, -==================================== -Contributing to CKAN's Documentation -==================================== +====================================== +Contributing to the CKAN Documentation +====================================== Note: getting started with contributing to `docs.ckan.org`_ is a little complicated. An easier way to contribute documentation to CKAN is to