-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Pull Request Template
M Starch edited this page Jul 30, 2020
·
3 revisions
Copy and paste this markdown into your newly created pull-request. Then ensure that the fields are filled in.
## F´ Pull Request
|**Field**|**Value**|
|:---|:---|
|**_Submission Date_**| |
|**_Submitter_**| |
|**_Originating Project/Creator_**| |
|**_Base Branch_**| |
|**_Short Description_**| |
|**_Affected Component_**| |
|**_Affected Architectures(s)_**| |
|**_Related Issue(s)_**| |
|**_Has Unit Tests (y/n)_**| |
|**_Build Checked (y/n)_**| |
|**_Unit Tests Run (y/n)_**| |
|**_Documentation Included (y/n)_**| |
---
## Change Description
## Rationale
## Testing Recommendations
## Future Work
Field | Value |
---|---|
Submission Date | 2019-01-08 |
Submitter | @mstarch |
Originating Project/Team | @mstarch |
Base Branch | devel |
Short Description | A contrived change as an example. |
Affected Component | Svc/FileDown |
Affected Architectures(s) | Linux |
Related Issue(s) | #1, #3, #16 |
Has Unit Tests (y/n) | y |
Build Checked (y/n) | y |
Unit Tests Run (y/n) | y |
Documentation Included (y/n) | y |
This adds nothing to the FileDown component, which fixes some fake issues. These additions change no files.
This change was needed to fix non-existent issues in the FileDown. When testing, FileDown was conclusively proven to not be broken and therefore required these (null) fixes.
Open up the file down component and check XYZ runs.
No future work expected based on this request.