Skip to content

Commit 048d53e

Browse files
committed
0 parents  commit 048d53e

File tree

569 files changed

+79946
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

569 files changed

+79946
-0
lines changed

.clang-format

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
AccessModifierOffset: -4
2+
AlignAfterOpenBracket: Align
3+
AlignConsecutiveAssignments: false
4+
AlignConsecutiveDeclarations: false
5+
AlignEscapedNewlinesLeft: false
6+
AlignTrailingComments: false
7+
AllowAllParametersOfDeclarationOnNextLine: true
8+
AllowShortFunctionsOnASingleLine: false
9+
AllowShortIfStatementsOnASingleLine: false
10+
AllowShortCaseLabelsOnASingleLine : false
11+
AllowShortLoopsOnASingleLine: false
12+
AlwaysBreakAfterDefinitionReturnType: false
13+
AlwaysBreakBeforeMultilineStrings: true
14+
AlwaysBreakTemplateDeclarations: true
15+
BinPackArguments: true
16+
BinPackParameters: false
17+
BreakBeforeBinaryOperators: false
18+
BreakBeforeBraces: Custom
19+
BraceWrapping:
20+
AfterClass: true
21+
AfterControlStatement: true
22+
AfterEnum: true
23+
AfterFunction: true
24+
AfterNamespace: true
25+
AfterObjCDeclaration: true
26+
AfterStruct: true
27+
AfterUnion: true
28+
AfterExternBlock: true
29+
BeforeCatch: true
30+
BeforeElse: true
31+
IndentBraces: false
32+
SplitEmptyFunction: true
33+
SplitEmptyRecord: true
34+
SplitEmptyNamespace : true
35+
BreakBeforeTernaryOperators: false
36+
BreakConstructorInitializersBeforeComma: false
37+
BreakStringLiterals: false
38+
ColumnLimit: 120
39+
CommentPragmas: ''
40+
ConstructorInitializerAllOnOneLineOrOnePerLine: true
41+
ConstructorInitializerIndentWidth: 4
42+
ContinuationIndentWidth: 4
43+
Cpp11BracedListStyle: false
44+
DerivePointerBinding: false
45+
FixNamespaceComments: true
46+
IndentCaseLabels: false
47+
IndentPPDirectives: AfterHash
48+
IndentFunctionDeclarationAfterType: false
49+
IndentWidth: 4
50+
SortIncludes: false
51+
IncludeCategories:
52+
- Regex: '[<"](.*\/)?defines.h[>"]'
53+
Priority: 1
54+
# - Regex: '<cuslide\/.+>'
55+
# Priority: 3
56+
- Regex: '<[[:alnum:]_.]+>'
57+
Priority: 5
58+
- Regex: '<[[:alnum:]_.\/]+>'
59+
Priority: 4
60+
- Regex: '".*"'
61+
Priority: 2
62+
IncludeBlocks: Regroup
63+
Language: Cpp
64+
MaxEmptyLinesToKeep: 2
65+
NamespaceIndentation: None
66+
ObjCSpaceAfterProperty: true
67+
ObjCSpaceBeforeProtocolList: true
68+
PenaltyBreakBeforeFirstCallParameter: 0
69+
PenaltyBreakComment: 1
70+
PenaltyBreakFirstLessLess: 0
71+
PenaltyBreakString: 1
72+
PenaltyExcessCharacter: 10
73+
PenaltyReturnTypeOnItsOwnLine: 1000
74+
PointerAlignment: Left
75+
SpaceBeforeAssignmentOperators: true
76+
SpaceBeforeParens: ControlStatements
77+
SpaceInEmptyParentheses: false
78+
SpacesBeforeTrailingComments: 1
79+
SpacesInAngles: false
80+
SpacesInCStyleCastParentheses: false
81+
SpacesInContainerLiterals: false
82+
SpacesInParentheses: false
83+
Standard: Cpp11
84+
ReflowComments: true
85+
TabWidth: 4
86+
UseTab: Never

.dockerignore

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
*
2+
!docker
3+
#cmake-build-*
4+
#build
5+
#install
6+
!temp/gds
7+

.editorconfig

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
[*]
2+
indent_style = space
3+
indent_size = 4
4+
charset = utf-8
5+
trim_trailing_whitespace = true
6+
max_line_length = 120
7+
insert_final_newline = true

.github/CODEOWNERS

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
#cpp code owners
2+
cpp/ @rapidsai/<repo>-cpp-codeowners
3+
4+
#python code owners
5+
python/ @rapidsai/<repo>-python-codeowners
6+
python/dask_cudf/ @rapidsai/<repo>-dask-codeowners
7+
8+
#cmake code owners
9+
**/CMakeLists.txt @rapidsai/<repo>-cmake-codeowners
10+
**/cmake/ @rapidsai/<repo>-cmake-codeowners
11+
12+
#build/ops code owners
13+
.github/ @rapidsai/ops-codeowners
14+
ci/ @rapidsai/ops-codeowners
15+
conda/ @rapidsai/ops-codeowners
16+
**/Dockerfile @rapidsai/ops-codeowners
17+
**/.dockerignore @rapidsai/ops-codeowners
18+
docker/ @rapidsai/ops-codeowners
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
name: Bug report
3+
about: Create a bug report to help us improve ___PROJECT___
4+
title: "[BUG]"
5+
labels: "? - Needs Triage, bug"
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**Steps/Code to reproduce bug**
14+
Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports to craft a minimal bug report. This helps us reproduce the issue you're having and resolve the issue more quickly.
15+
16+
**Expected behavior**
17+
A clear and concise description of what you expected to happen.
18+
19+
**Environment details (please complete the following information):**
20+
- Environment location: [Bare-metal, Docker, Cloud(specify cloud provider)]
21+
- Method of ___PROJECT___ install: [conda, Docker, or from source]
22+
- If method of install is [Docker], provide `docker pull` & `docker run` commands used
23+
24+
25+
**Additional context**
26+
Add any other context about the problem here.
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
name: Documentation request
3+
about: Report incorrect or needed documentation
4+
title: "[DOC]"
5+
labels: "? - Needs Triage, doc"
6+
assignees: ''
7+
8+
---
9+
10+
## Report incorrect documentation
11+
12+
**Location of incorrect documentation**
13+
Provide links and line numbers if applicable.
14+
15+
**Describe the problems or issues found in the documentation**
16+
A clear and concise description of what you found to be incorrect.
17+
18+
**Steps taken to verify documentation is incorrect**
19+
List any steps you have taken:
20+
21+
**Suggested fix for documentation**
22+
Detail proposed changes to fix the documentation if you have any.
23+
24+
---
25+
26+
## Report needed documentation
27+
28+
**Report needed documentation**
29+
A clear and concise description of what documentation you believe it is needed and why.
30+
31+
**Describe the documentation you'd like**
32+
A clear and concise description of what you want to happen.
33+
34+
**Steps taken to search for needed documentation**
35+
List any steps you have taken:
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for ___PROJECT___
4+
title: "[FEA]"
5+
labels: "? - Needs Triage, feature request"
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I wish I could use ___PROJECT___ to do [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context, code examples, or references to existing implementations about the feature request here.
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: Submit question
3+
about: Ask a general question about ___PROJECT___
4+
title: "[QST]"
5+
labels: "? - Needs Triage, question"
6+
assignees: ''
7+
8+
---
9+
10+
**What is your question?**

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
<!--
2+
3+
Thank you for contributing to ___PROJECT___ :)
4+
5+
Here are some guidelines to help the review process go smoothly.
6+
7+
1. Please write a description in this text box of the changes that are being
8+
made.
9+
10+
2. Please ensure that you have written units tests for the changes made/features
11+
added.
12+
13+
3. If you are closing an issue please use one of the automatic closing words as
14+
noted here: https://help.github.com/articles/closing-issues-using-keywords/
15+
16+
4. If your pull request is not ready for review but you want to make use of the
17+
continuous integration testing facilities please label it with `[WIP]`.
18+
19+
5. If your pull request is ready to be reviewed without requiring additional
20+
work on top of it, then remove the `[WIP]` label (if present) and replace
21+
it with `[REVIEW]`. If assistance is required to complete the functionality,
22+
for example when the C/C++ code of a feature is complete but Python bindings
23+
are still required, then add the label `[HELP-REQ]` so that others can triage
24+
and assist. The additional changes then can be implemented on top of the
25+
same PR. If the assistance is done by members of the rapidsAI team, then no
26+
additional actions are required by the creator of the original PR for this,
27+
otherwise the original author of the PR needs to give permission to the
28+
person(s) assisting to commit to their personal fork of the project. If that
29+
doesn't happen then a new PR based on the code of the original PR can be
30+
opened by the person assisting, which then will be the PR that will be
31+
merged.
32+
33+
6. Once all work has been done and review has taken place please do not add
34+
features or make changes out of the scope of those requested by the reviewer
35+
(doing this just add delays as already reviewed code ends up having to be
36+
re-reviewed/it is hard to tell what is new etc!). Further, please do not
37+
rebase your branch on main/force push/rewrite history, doing any of these
38+
causes the context of any comments made by reviewers to be lost. If
39+
conflicts occur against main they should be resolved by merging main
40+
into the branch used for making the pull request.
41+
42+
Many thanks in advance for your cooperation!
43+
44+
-->

0 commit comments

Comments
 (0)