File: pull_request_template

package info (click to toggle)
ilorest 5.2.0.0-7
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 12,668 kB
  • sloc: python: 45,028; javascript: 10,504; sh: 3,041; makefile: 301; ruby: 204
file content (34 lines) | stat: -rw-r--r-- 1,442 bytes parent folder | download | duplicates (2)
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
<p>&mdash;&ndash;Synopsis of Commits Above&mdash;&ndash;</p>

<p><strong>Please fill out the following when submitting the PR</strong></p>

<h2 id="status">Status</h2>

<ul>
<li>[ ] READY </li>
<li>[ ] IN-DEVELOPMENT </li>
<li>[ ] ON-HOLD</li>
</ul>

<h2 id="description">Description</h2>

<p>A few sentences describing the overall goals of the pull request&rsquo;s commits.
- Include the issue number here if it fixes one. Example <code class="prettyprint">#1</code>
- Include the QUIX number here if it fixes one.</p>

<h2 id="dependent-prs">Dependent PRs</h2>

<p>List any PRs that must be merged together. Please note if order must be preserved. (For example if there are library changes needed)
- If additional tool PRs are to be referenced simply note the PR#
- If library PRs are to be referenced note &ldquo;library&rdquo; followed by the PR# </p>

<h2 id="before-status-can-be-set-to-ready-i-have-completed-at-least-one-of-the-following">Before Status can be set to READY I have completed at least ONE of the following:</h2>

<ul>
<li>[ ] Check if documentation updates</li>
<li>[ ] Check if example code updates</li>
<li>[ ] Pylint static analysistests are passing above 9.0/10.0</li>
<li>[N/A] Unit tests added for any new functions/features (Not required yet)</li>
<li>[ ] Automatic testing passed</li>
<li>[ ] Targeted/Custom Testing performed. Indicate the results in the description above or as additional comments.</li>
</ul>