mirror of
https://github.com/git/git
synced 2024-11-05 18:59:29 +00:00
09dad9256a
It's typical to find Markdown documentation alongside source code, and
having better context for documentation changes is useful; see also
commit
|
||
|---|---|---|
| .. | ||
| cpp-c++-function | ||
| cpp-class-constructor | ||
| cpp-class-constructor-mem-init | ||
| cpp-class-definition | ||
| cpp-class-definition-derived | ||
| cpp-class-destructor | ||
| cpp-function-returning-global-type | ||
| cpp-function-returning-nested | ||
| cpp-function-returning-pointer | ||
| cpp-function-returning-reference | ||
| cpp-gnu-style-function | ||
| cpp-namespace-definition | ||
| cpp-operator-definition | ||
| cpp-skip-access-specifiers | ||
| cpp-skip-comment-block | ||
| cpp-skip-labels | ||
| cpp-struct-definition | ||
| cpp-struct-single-line | ||
| cpp-template-function-definition | ||
| cpp-union-definition | ||
| cpp-void-c-function | ||
| css-brace-in-col-1 | ||
| css-colon-eol | ||
| css-colon-selector | ||
| css-common | ||
| css-long-selector-list | ||
| css-prop-sans-indent | ||
| css-short-selector-list | ||
| css-trailing-space | ||
| custom1-pattern | ||
| custom2-match-to-end-of-line | ||
| custom3-alternation-in-pattern | ||
| dts-labels | ||
| dts-node-unitless | ||
| dts-nodes | ||
| dts-nodes-boolean-prop | ||
| dts-nodes-comment1 | ||
| dts-nodes-comment2 | ||
| dts-nodes-multiline-prop | ||
| dts-reference | ||
| dts-root | ||
| dts-root-comment | ||
| elixir-do-not-pick-end | ||
| elixir-ex-unit-test | ||
| elixir-function | ||
| elixir-macro | ||
| elixir-module | ||
| elixir-module-func | ||
| elixir-nested-module | ||
| elixir-private-function | ||
| elixir-protocol | ||
| elixir-protocol-implementation | ||
| fountain-scene | ||
| golang-complex-function | ||
| golang-func | ||
| golang-interface | ||
| golang-long-func | ||
| golang-struct | ||
| java-class-member-function | ||
| markdown-heading-indented | ||
| markdown-heading-non-headings | ||
| matlab-class-definition | ||
| matlab-function | ||
| matlab-octave-section-1 | ||
| matlab-octave-section-2 | ||
| matlab-section | ||
| perl-skip-end-of-heredoc | ||
| perl-skip-forward-decl | ||
| perl-skip-sub-in-pod | ||
| perl-sub-definition | ||
| perl-sub-definition-kr-brace | ||
| php-abstract-class | ||
| php-class | ||
| php-final-class | ||
| php-function | ||
| php-interface | ||
| php-method | ||
| php-trait | ||
| python-async-def | ||
| python-class | ||
| python-def | ||
| python-indented-async-def | ||
| python-indented-class | ||
| python-indented-def | ||
| README | ||
| rust-fn | ||
| rust-impl | ||
| rust-struct | ||
| rust-trait | ||
How to write RIGHT test cases ============================= Insert the word "ChangeMe" (exactly this form) at a distance of at least two lines from the line that must appear in the hunk header. The text that must appear in the hunk header must contain the word "right", but in all upper-case, like in the title above. To mark a test case that highlights a malfunction, insert the word BROKEN in all lower-case somewhere in the file. This text is a bit twisted and out of order, but it is itself a test case for the default hunk header pattern. Know what you are doing if you change it. BTW, this tests that the head line goes to the hunk header, not the line of equal signs.