@@ -29,59 +29,59 @@ $ docker build --check .
29
29
</thead >
30
30
<tbody >
31
31
<tr>
32
- <td><a href="./stage-name-casing.md ">StageNameCasing</a></td>
32
+ <td><a href="./stage-name-casing/ ">StageNameCasing</a></td>
33
33
<td>Stage names should be lowercase</td>
34
34
</tr>
35
35
<tr>
36
- <td><a href="./from-as-casing.md ">FromAsCasing</a></td>
36
+ <td><a href="./from-as-casing/ ">FromAsCasing</a></td>
37
37
<td>The 'as' keyword should match the case of the 'from' keyword</td>
38
38
</tr>
39
39
<tr>
40
- <td><a href="./no-empty-continuation.md ">NoEmptyContinuation</a></td>
40
+ <td><a href="./no-empty-continuation/ ">NoEmptyContinuation</a></td>
41
41
<td>Empty continuation lines will become errors in a future release</td>
42
42
</tr>
43
43
<tr>
44
- <td><a href="./consistent-instruction-casing.md ">ConsistentInstructionCasing</a></td>
44
+ <td><a href="./consistent-instruction-casing/ ">ConsistentInstructionCasing</a></td>
45
45
<td>Instructions should be in consistent casing (all lower or all upper)</td>
46
46
</tr>
47
47
<tr>
48
- <td><a href="./file-consistent-command-casing.md ">FileConsistentCommandCasing</a></td>
48
+ <td><a href="./file-consistent-command-casing/ ">FileConsistentCommandCasing</a></td>
49
49
<td>All commands within the Dockerfile should use the same casing (either upper or lower)</td>
50
50
</tr>
51
51
<tr>
52
- <td><a href="./duplicate-stage-name.md ">DuplicateStageName</a></td>
52
+ <td><a href="./duplicate-stage-name/ ">DuplicateStageName</a></td>
53
53
<td>Stage names should be unique</td>
54
54
</tr>
55
55
<tr>
56
- <td><a href="./reserved-stage-name.md ">ReservedStageName</a></td>
56
+ <td><a href="./reserved-stage-name/ ">ReservedStageName</a></td>
57
57
<td>Reserved words should not be used as stage names</td>
58
58
</tr>
59
59
<tr>
60
- <td><a href="./json-args-recommended.md ">JSONArgsRecommended</a></td>
60
+ <td><a href="./json-args-recommended/ ">JSONArgsRecommended</a></td>
61
61
<td>JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals</td>
62
62
</tr>
63
63
<tr>
64
- <td><a href="./maintainer-deprecated.md ">MaintainerDeprecated</a></td>
64
+ <td><a href="./maintainer-deprecated/ ">MaintainerDeprecated</a></td>
65
65
<td>The MAINTAINER instruction is deprecated, use a label instead to define an image author</td>
66
66
</tr>
67
67
<tr>
68
- <td><a href="./undefined-arg-in-from.md ">UndefinedArgInFrom</a></td>
68
+ <td><a href="./undefined-arg-in-from/ ">UndefinedArgInFrom</a></td>
69
69
<td>FROM command must use declared ARGs</td>
70
70
</tr>
71
71
<tr>
72
- <td><a href="./workdir-relative-path.md ">WorkdirRelativePath</a></td>
72
+ <td><a href="./workdir-relative-path/ ">WorkdirRelativePath</a></td>
73
73
<td>Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes</td>
74
74
</tr>
75
75
<tr>
76
- <td><a href="./undefined-var.md ">UndefinedVar</a></td>
76
+ <td><a href="./undefined-var/ ">UndefinedVar</a></td>
77
77
<td>Variables should be defined before their use</td>
78
78
</tr>
79
79
<tr>
80
- <td><a href="./multiple-instructions-disallowed.md ">MultipleInstructionsDisallowed</a></td>
80
+ <td><a href="./multiple-instructions-disallowed/ ">MultipleInstructionsDisallowed</a></td>
81
81
<td>Multiple instructions of the same type should not be used in the same stage</td>
82
82
</tr>
83
83
<tr>
84
- <td><a href="./legacy-key-value-format.md ">LegacyKeyValueFormat</a></td>
84
+ <td><a href="./legacy-key-value-format/ ">LegacyKeyValueFormat</a></td>
85
85
<td>Legacy key/value format with whitespace separator should not be used</td>
86
86
</tr>
87
87
</tbody >
0 commit comments