Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | CONTRIBUTING: Fix typos and spelling | Josef Angstenberger | 2021-05-07 | 1 | -1/+1 |
| | |||||
* | Help: Update contributor instructions to refer to the forum | Craig Scott | 2020-05-23 | 1 | -2/+2 |
| | | | Fixes: #20746 | ||||
* | CONTRIBUTING: Clarify creation of topic branch from target branch | Brad King | 2019-08-30 | 1 | -2/+3 |
| | | | | | | The sentence "Base all new work on the upstream master branch." may be interpreted to mean that one should commit on a 'master' branch. Precede this with an explicit step for creating a topic branch. | ||||
* | Help: Insert link from CONTRIBUTING to build instructions | Joachim Wuttke (h) | 2018-12-18 | 1 | -1/+3 |
| | |||||
* | Help: Update maintainer edit checkbox label | Craig Scott | 2018-08-06 | 1 | -1/+3 |
| | | | | | | Recent GitLab updates have changed the label associated with the checkbox in merge request descriptions for allowing edits from maintainers. Make the contributor guidelines match the new label and add a note for why it is recommended. | ||||
* | contributing: Document that anyone can contribute testing machine | Jean-Christophe Fillion-Robin | 2018-08-05 | 1 | -0/+14 |
| | |||||
* | CONTRIBUTING: Mention GitLab option to allow edits from maintainers | Brad King | 2018-04-12 | 1 | -0/+1 |
| | | | | | Collaboration between contributors and developers is easier if a developer can push an update to a contributor's MR source branch. | ||||
* | CONTRIBUTING: Clarify choice of master or release branch as a base | Jean-Christophe Fillion-Robin | 2018-03-15 | 1 | -0/+2 |
| | |||||
* | Help/dev: Add commit message guidelines | Craig Scott | 2017-08-08 | 1 | -1/+3 |
| | |||||
* | CONTRIBUTING: Explain how to propose changes to the release branch | Brad King | 2017-07-21 | 1 | -1/+4 |
| | |||||
* | Help/dev: Adopt clang-format instructions in coding guide | Brad King | 2017-04-19 | 1 | -12/+2 |
| | | | | | Simplify the `CONTRIBUTING.rst` document by moving the code style section over to our dedicated coding guide and linking to it instead. | ||||
* | CONTRIBUTING: Add link to review process document | Brad King | 2017-03-03 | 1 | -0/+3 |
| | |||||
* | CONTRIBUTING: Add link to development documentation README | Brad King | 2017-03-03 | 1 | -0/+5 |
| | |||||
* | CONTRIBUTING: Add note about running developer setup script | Brad King | 2017-03-03 | 1 | -0/+2 |
| | |||||
* | CONTRIBUTING: Document contribution through the Kitware GitLab Instance | Brad King | 2016-09-28 | 1 | -9/+13 |
| | | | | | Replace the instructions that routed patches to the mailing list with new instructions routing them to our GitLab instance. | ||||
* | CONTRIBUTING: Reference clang-format helper script for code style | Brad King | 2016-09-28 | 1 | -0/+2 |
| | |||||
* | CONTRIBUTING: Add a section on coding style | Brad King | 2016-05-16 | 1 | -0/+10 |
| | | | | Document that we now define our coding style with `clang-format`. | ||||
* | Replace http://www.cmake.org URLs with https://cmake.org | Brad King | 2015-09-25 | 1 | -1/+1 |
| | | | | | | | The latter is now the preferred URL for visiting cmake.org with a browser. Convert using the shell code: git ls-files -z | xargs -0 sed -i 's|http://www\.cmake|https://cmake|g' | ||||
* | CONTRIBUTING: Spell "offered" correctly | Brad King | 2015-07-02 | 1 | -1/+1 |
| | | | | Reported-by: Radovan Bast | ||||
* | Simplify and clarify credit text and link | Brad King | 2014-06-03 | 1 | -2/+2 |
| | | | | | Use the name "Kitware" rather than "Kitware, Inc." to simplify the text. Provide a CMake-specific URL. | ||||
* | README: Credit Kitware and community of contributors | Brad King | 2014-02-03 | 1 | -0/+5 |
| | |||||
* | Update README and add guidelines for CONTRIBUTING | Brad King | 2014-01-29 | 1 | -0/+29 |
Rename 'Readme.txt' to 'README.rst', format the documentation as reStructuredText, and modernize the content. Also add a new 'CONTRIBUTING.rst' explaining the preferred entry path for new contributors. |