Skip to content

Conversation

@karthikvetrivel
Copy link
Member

Description

Add a PR template to ensure contributors document how changes were tested and for general documentation purposes.

Context (optional)

We currently have no PR template. This makes it easy for PRs to slip through without adequate testing documentation.

Testing

  • Additional unit tests (make test)
  • E2E tests (describe below)
  • Manual cluster testing (describe below)
  • N/A (docs, CI config, etc.)

Test details:
Adding GitHub config file only - no code changes.

Copy link
Contributor

@rajathagasthya rajathagasthya left a comment

Choose a reason for hiding this comment

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

LGTM.

<!-- How was this tested? e.g., unit tests, e2e tests, manual testing on cluster -->

- [ ] Additional unit tests (`make test`)
- [ ] E2E tests (describe below)
Copy link
Contributor

Choose a reason for hiding this comment

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

I am not sure what this means. The E2E tests are written by us, so when we ask PR contributors to elaborate further, are we assuming that they've written their own E2E tests?

Copy link
Member Author

Choose a reason for hiding this comment

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

I originally meant this field for if users add their own E2E tests, but this is an unlikely scenario. I added an "Other" field along with "N/A".

@karthikvetrivel karthikvetrivel force-pushed the add-pr-template branch 2 times, most recently from c8d343e to 5506b9b Compare December 8, 2025 19:13

<!-- Brief description of the change -->

## Context (optional)
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we need a separate section. Description can include the background or set the context of a change that a contributor intends to make

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated.


<!-- How was this tested? e.g., unit tests, e2e tests, manual testing on cluster -->

- [ ] Unit tests (`make test`)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- [ ] Unit tests (`make test`)
- [ ] Unit tests (`make coverage`)

Copy link
Contributor

Choose a reason for hiding this comment

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

make coverage is the superset of make test

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated.


- [ ] No secrets, sensitive information, or unrelated changes
- [ ] Code style followed (`make lint`)
- [ ] Tests/documentation updated if applicable
Copy link
Contributor

Choose a reason for hiding this comment

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

This is already covered by the section below

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated.

## Checklist

- [ ] No secrets, sensitive information, or unrelated changes
- [ ] Code style followed (`make lint`)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- [ ] Code style followed (`make lint`)
- [ ] Lint checks passing (`make lint`)

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated.

@tariq1890
Copy link
Contributor

tariq1890 commented Dec 8, 2025

Under Checklist, let's add the following as well:

  • Ensure generated assets are updated and in-sync (make validate-generated-assets)
  • Ensure go mod artifacts are updated and in-sync (make validate-modules)

Signed-off-by: Karthik Vetrivel <kvetrivel@nvidia.com>
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.

4 participants