When working on #414 it was noted that there are both .yml files and .yaml files, in the repository, which was a source of some confusion. Considering renaming files (and changing any references to those files) for consistency.
Time Estimate
1 to 3 days of work
Sub-Issues
Consider breaking the task down into sub-issues.
[ ] Add a checkbox for each sub-issue here.
Relevant Deadlines
NONE
Funding Source
TBD
Define the Metadata
Assignee
[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required
Labels
[x] Select component(s)
[x] Select priority
[x] Select requestor(s)
Projects and Milestone
[x] Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
[x] Select Milestone as the next official version or Future Versions
Define Related Issue(s)
Consider the impact to the other METplus components.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
Describe the Task
When working on #414 it was noted that there are both .yml files and .yaml files, in the repository, which was a source of some confusion. Considering renaming files (and changing any references to those files) for consistency.
Time Estimate
1 to 3 days of work
Sub-Issues
Consider breaking the task down into sub-issues.
Relevant Deadlines
NONE
Funding Source
TBD
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Task Checklist
See the METplus Workflow for details.
feature_<Issue Number>_<Description>
feature <Issue Number> <Description>