blob: 478dd566f5cb49fea27bfbfb1a4cb5c25f19c6cb (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
Contributing
============
Overview
--------
- Update `NEWS.md.in`.
- Update `.mailmap`.
- Write a test covering your feature or fix.
- Ensure existing and new tests are passing.
- Submit a pull request on GitHub.
Explanation
-----------
Consider updating `NEWS.md.in`. The topmost section is for the upcoming
release. Bugfixes should be marked with `BUGFIX`. Small things (typos,
code style) should be grouped but with multiple authors (`Documentation
updates thanks to Dan Croak and Roberto Pedroso`).
We use your name and email address as produced by `git-shortlog(1)`. You
can change how this is formatted by modifying `.mailmap`. More details
on that file can be found in the git [Documentation/mailmap.txt][mailmap].
Our test suite is new, and therefore it is not yet mandatory to include
tests with pull requests. However, you must ensure that the existing
test suite passes with any changes you make. Also, any attempts to add
or extend tests will increase the chances of your pull request being
merged.
Submit a pull request using GitHub. If there is a relevant bug, mention
it in the commit message (`Fixes #42.`).
[mailmap]: https://github.com/git/git/blob/6a907786af835ac15962be53f1492f2
Testing
-----
The test suite uses [cram][]. It is an integration suite, meaning the
programs are exercised from the outside and assertions are made only on
their output or effects.
All tests can be run like so:
$ make check
Individual tests can be run like so:
$ env TESTS=lsrc-dotfiles-dirs.t make -e check
If you intend to write a new test:
1. Add your test at `test/subcommand-something-meaningful.t`.
2. Add the relative name to the `TESTS` variable in `test/Makefile.am`.
3. Source `test/helper.sh` as the first line of your test.
4. When in doubt, use existing tests as a guide.
[cram]: https://bitheap.org/cram/
|
