-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
31 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Code of Conduct | ||
|
||
The tt-torch project follows the Code of Conduct for tt-mlir project that can be found at: <https://tenstorrent.github.io/tt-mlir/code-of-conduct.html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# Contributing guidelines for TT-Torch | ||
|
||
## PR Guidelines | ||
### Community contributions | ||
Thank you for your interest in the TT-Torch project we appreciate your support. | ||
For all PRs we have an internal policy listed below which your PR will go through after an initial review has been done. | ||
|
||
The initial review will encompase the following: | ||
* Review the PR for CI / CD Readiness. Includes making sure that the code and PR at a high level makes sense for the project | ||
* Once approved for CI / CD readiness a Tenstorrent developer will kick off our CI/CD pipeline on your behalf. | ||
|
||
### Internal contributions | ||
For internal contributions we have the following guidelines: | ||
|
||
* A 24 hour merge rule exists. The rule is to wait at least 24 hours since the PR was initially opened for review. This gives members of our teams that span the globe opportunity to provide feedback to PRs. | ||
|
||
In addition to the 24 hour rule the following prerequisites for landing PR exist: | ||
* At least 1 reviewer signs off on the change | ||
* Component owner sign offs (github will tell you if this hasn't been met) | ||
* Green CI | ||
* Wait at least 24 hours since opening the PR to give all tagged reviewers a chance to take a look. Or at least comment on the issue that they need more time to review. | ||
* *Rebasing or further changes to the PR do not reset the 24 hour counter.* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters