mirror of
https://github.com/nasa/openmct.git
synced 2024-12-18 20:57:53 +00:00
ceeb761d94
* include package lock * migrate to npm ci * remove cache busting doc and replace with npm run clean --------- Co-authored-by: Jesse Mazzella <jesse.d.mazzella@nasa.gov> Co-authored-by: Andrew Henry <akhenry@gmail.com>
29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
<!--- Note: Please open the PR in draft form until you are ready for active review. -->
|
|
Closes <!--- Insert Issue Number(s) this PR addresses. Start by typing # will open a dropdown of recent issues. Note: this does not work on PRs which target release branches -->
|
|
|
|
### Describe your changes:
|
|
<!--- Describe your changes and add any comments about your approach either here or inline if code comments aren't added -->
|
|
|
|
### All Submissions:
|
|
|
|
* [ ] Have you followed the guidelines in our [Contributing document](https://github.com/nasa/openmct/blob/master/CONTRIBUTING.md)?
|
|
* [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/nasa/openmct/pulls) for the same update/change?
|
|
* [ ] Is this a [notable change](../docs/src/process/release.md) that will require a special callout in the release notes? For example, will this break compatibility with existing APIs or projects that consume these plugins?
|
|
|
|
### Author Checklist
|
|
|
|
* [ ] Changes address original issue?
|
|
* [ ] Tests included and/or updated with changes?
|
|
* [ ] Has this been smoke tested?
|
|
* [ ] Have you associated this PR with a `type:` label? Note: this is not necessarily the same as the original issue.
|
|
* [ ] Have you associated a milestone with this PR? Note: leave blank if unsure.
|
|
* [ ] Testing instructions included in associated issue OR is this a dependency/testcase change?
|
|
|
|
### Reviewer Checklist
|
|
|
|
* [ ] Changes appear to address issue?
|
|
* [ ] Reviewer has tested changes by following the provided instructions?
|
|
* [ ] Changes appear not to be breaking changes?
|
|
* [ ] Appropriate automated tests included?
|
|
* [ ] Code style and in-line documentation are appropriate?
|