Mercurial > vim

comparison CONTRIBUTING.md @ 17640:c12c811695f7 v8.1.1817

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.1.1817: github contribution text is incomplete commit https://github.com/vim/vim/commit/6f33b893c6c5f4881ca60e12cb81a3ec31eae7ab Author: Bram Moolenaar <Bram@vim.org> Date: Sun Aug 4 23:22:08 2019 +0200 patch 8.1.1817: github contribution text is incomplete Problem: Github contribution text is incomplete. Solution: Update the text.
author Bram Moolenaar <Bram@vim.org>
date Sun, 04 Aug 2019 23:30:05 +0200
parents e71261a88630
children daa71bf6b546
comparison
equal deleted inserted replaced
17639:9b97b010f12f 17640:c12c811695f7
2 2
3 Patches are welcome in whatever form. 3 Patches are welcome in whatever form.
4 Discussions about patches happen on the vim-dev maillist. 4 Discussions about patches happen on the vim-dev maillist.
5 If you create a pull request on GitHub it will be 5 If you create a pull request on GitHub it will be
6 forwarded to the vim-dev maillist. You can also send your patch there 6 forwarded to the vim-dev maillist. You can also send your patch there
7 directly. An attachment with a unified diff format is preferred. 7 directly. In that case an attachment with a unified diff format is preferred.
8 Information about the maillist can be found [on the Vim website]. 8 Information about the maillist can be found [on the Vim website].
9 9
10 [on the Vim website]: http://www.vim.org/maillist.php#vim-dev 10 [on the Vim website]: http://www.vim.org/maillist.php#vim-dev
11 11
12 Please consider adding a test. Test coverage isn't very good yet, this needs 12 A pull request has the advantage that it will trigger the Continuous
13 to improve. Look through recent patches for examples. The tests are located 13 Integration tests, you will be warned of problems (you can ignore the coverage
14 under "src/testdir". 14 warning, it's noisy).
15
16 Please consider adding a test. All new functionality should be tested and bug
17 fixes should be tested for regressions: the test should fail before the fix and
18 pass after the fix. Look through recent patches for examples and find help
19 with ":help testing". The tests are located under "src/testdir".
20
21 Contributions will be distributed with Vim under the Vim license. Providing a
22 change to be included implies that you agree with this and your contribution
23 does not cause us trouble with trademarks or patents. There is no CLA to sign.
15 24
16 25
17 # Reporting issues 26 # Reporting issues
18 27
19 We use GitHub issues, but that is not a requirement. Writing to the Vim 28 We use GitHub issues, but that is not a requirement. Writing to the Vim