Skip to content

Part nasa/cFS#1079, Adding specialty PR templates and links to the specialty PR templates in the default PR template. - #183

Open
dzbaker wants to merge 2 commits into
nasa:devfrom
dzbaker:fix1079
Open

Part nasa/cFS#1079, Adding specialty PR templates and links to the specialty PR templates in the default PR template.#183
dzbaker wants to merge 2 commits into
nasa:devfrom
dzbaker:fix1079

Conversation

@dzbaker

@dzbaker dzbaker commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Description of Change

Adding specialty PR templates to this repository and adding links to these templates in the default PR template.

Linked Issue

Partially Closes nasa/cFS#1079

Areas of Expertise Touched

  • ASTRO
  • CI/CD
  • COSMOS
  • Cybersecurity
  • Docker
  • EDS
  • Git
  • PSPs
  • SBN
  • SMP
  • Tables
  • TSN
  • Unit Tests
  • Other

Author Checklist

  • Linked GitHub issue is referenced above/linked to this PR
  • Documentation generation workflow ran successfully on this branch
  • Changes are limited to documentation/comments (no code behavior changes)

Reviewer Checklist

  • Documentation is clear, accurate, and complete
  • Spelling and grammar reviewed
  • Any links in the documentation have been verified to work
  • Documentation generation workflow output looks correct
  • Appropriate Expert areas have been reviewed

…ecialty PR templates in the default PR template.
<!-- Required. Reference the GitHub issue this PR addresses, e.g., Closes #123 -->
Closes #

## Areas of Expertise Touched

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A link to the expertise Excel file would be helpful for determining who to contact


---

## Author Checklist

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add something like "Commit history squashed"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed at 8/3/2026 stand up and team decided to place commit squashing guidance in a central "Pull Request Guide," as the commit history should/should not be squashed depending on the circumstances. This is being tracked in nasa/cFE#2788 and the PR templates will be updated accordingly once that guide has been created.

## Requirements Impact

<!-- List any requirements impacted by this change. Indicate whether each was updated, or confirm the change continues to satisfy existing requirements. -->
- Requirement ID(s):

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A link to the requirements would be helpful

### COSMOS Test Suite
<!-- Link to CI run, paste summary, or note "N/A — no relevant changes" -->

## Areas of Expertise Touched

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A link to the expertise Excel file would be helpful for determining who to contact


---

## Author Checklist

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add something like "Commit history squashed"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed at 8/3/2026 stand up and team decided to place commit squashing guidance in a central "Pull Request Guide," as the commit history should/should not be squashed depending on the circumstances. This is being tracked in nasa/cFE#2788 and the PR templates will be updated accordingly once that guide has been created.

## Reviewer Checklist

- [ ] Code logic is correct and matches the stated intent
- [ ] Code is readable, maintainable, and follows project conventions

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you link the coding standards here?

Comment on lines +71 to +72
- [ ] Unit tests are meaningful and adequately cover the changes
- [ ] **The change has been exercised by the unit tests** (not just that tests pass — the new/changed code paths are actually covered)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How are these different?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed!


Closes #

## Areas of Expertise Touched

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A link to the expertise Excel file would be helpful for determining who to contact


---

## Author Checklist

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add something like "Commit history squashed"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed at 8/3/2026 stand up and team decided to place commit squashing guidance in a central "Pull Request Guide," as the commit history should/should not be squashed depending on the circumstances. This is being tracked in nasa/cFE#2788 and the PR templates will be updated accordingly once that guide has been created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants