Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding license, and contributing guidelines from #72 and #65 #74

Merged
merged 6 commits into from
Aug 7, 2024

Conversation

jstjohn
Copy link
Collaborator

@jstjohn jstjohn commented Aug 2, 2024

Address issue #72 and #65.

@jstjohn jstjohn requested review from pstjohn and nehap25 August 2, 2024 22:15
@jstjohn jstjohn self-assigned this Aug 2, 2024
@jstjohn
Copy link
Collaborator Author

jstjohn commented Aug 2, 2024

/build-ci

CONTRIBUTING.md Show resolved Hide resolved
Comment on lines +165 to +172
Add unit tests under `tests` to examine use cases of new classes or methods that are being added to the codebase. Each
test file must be for a particular file or module. For example if you have a file that is under
`src/path/to/module/my_file_name.py` then your test should match the path at `tests/path/to/module/test_my_file_name.py`.
Check the tests folders in the sub-modules of this repository for examples. If you are testing a module, such as
integrating multiple examples of different files, then you can use the following pattern to test the module, say in the
above example, if you wanted to test functions from several files together that all exist in the same `src/path/to/module`
then you could create a `tests/path/to/test_module.py` file. The same is true for parents of that module and so on.
Generally unit tests should exist at the level of the individual file however.
Copy link
Collaborator

Choose a reason for hiding this comment

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

This can wait, but at some point if we get larger it would be good to have a short section on "what makes a good test". Specifically, it would be nice to talk about test naming, self-contained tests, and short runtimes as being important. Eventually it would be nice to break out integration / gpu-dependent tests into their own bucket as well

CONTRIBUTING.md Outdated Show resolved Hide resolved
Comment on lines +65 to +72
* To sign off on a commit you simply use the `--signoff` (or `-s`) option when committing your changes:
```bash
$ git commit -s -m "Add cool feature."
```
This will append the following to your commit message:
```
Signed-off-by: Your Name <[email protected]>
```
Copy link
Collaborator

Choose a reason for hiding this comment

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

it would help to add guidance on how to retroactively sign commits.

Copy link
Collaborator

@skothenhill-nv skothenhill-nv left a comment

Choose a reason for hiding this comment

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

The sign-off workflow is really painful. If you don't sign every commit as you go, you essentially have to rebase every commit in a PR before it can be merged. Are there alternatives? Could we squash/sign when we merge a PR?

jstjohn added 2 commits August 7, 2024 15:35
Signed-off-by: John St John <[email protected]>
@skothenhill-nv
Copy link
Collaborator

The sign-off workflow is really painful. If you don't sign every commit as you go, you essentially have to rebase every commit in a PR before it can be merged. Are there alternatives? Could we squash/sign when we merge a PR?

Just a note, we have a googledoc and devcontainer setup for this now.

@jstjohn
Copy link
Collaborator Author

jstjohn commented Aug 7, 2024

/build-ci

@jstjohn jstjohn enabled auto-merge (squash) August 7, 2024 16:16
@jstjohn
Copy link
Collaborator Author

jstjohn commented Aug 7, 2024

/build-ci

@jstjohn jstjohn disabled auto-merge August 7, 2024 16:18
@jstjohn jstjohn enabled auto-merge (squash) August 7, 2024 16:18
@jstjohn jstjohn disabled auto-merge August 7, 2024 16:30
@jstjohn jstjohn merged commit 6a7271d into v2-main Aug 7, 2024
2 checks passed
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.

3 participants