Skip to content

Commit 5325fdc

Browse files
liu-hm19liu-hm19
committed
feat: a good start with kusion v0.13.0 apis
0 parents  commit 5325fdc

File tree

20 files changed

+1545
-0
lines changed

20 files changed

+1545
-0
lines changed

‎.github/ISSUE_TEMPLATE/bug-report.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: "\U0001F41B Bug Report"
3+
about: As a User, I want to report a Bug.
4+
labels: type/bug
5+
---
6+
7+
## Bug Report
8+
9+
Please answer these questions before submitting your issue. Thanks!
10+
11+
### 1. Minimal reproduce step (Required)
12+
13+
<!-- a step by step guide for reproducing the bug. -->
14+
15+
### 2. What did you expect to see? (Required)
16+
17+
### 3. What did you see instead (Required)
18+
19+
### 4. What is your KusionStack components version? (Required)
20+
21+
<!-- Paste the output of Kusion/kclvm-go/KCLVM version -->

‎.github/ISSUE_TEMPLATE/enhancement.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
name: "\U0001F680 Enhancement"
3+
about: As a KusionStack developer, I want to make an enhancement.
4+
labels: type/enhancement
5+
---
6+
7+
## Enhancement

‎.github/ISSUE_TEMPLATE/feature-request.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: "\U0001F680 Feature Request"
3+
about: As a user, I want to request a New Feature on the product.
4+
labels: type/feature-request
5+
---
6+
7+
## Feature Request
8+
9+
**Is your feature request related to a problem? Please describe:**
10+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
11+
12+
**Describe the feature you'd like:**
13+
<!-- A clear and concise description of what you want to happen. -->
14+
15+
**Describe alternatives you've considered:**
16+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
17+
18+
**Teachability, Documentation, Adoption, Migration Strategy:**
19+
<!-- If you can, explain some scenarios how users might use this, situations it would be helpful in. Any API designs, mockups, or diagrams are also helpful. -->

‎.github/ISSUE_TEMPLATE/general-question.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
name: "\U0001F914 Ask a Question"
3+
about: I want to ask a question.
4+
labels: type/question
5+
---
6+
7+
## General Question
8+
9+
<!--
10+
11+
Before asking a question, make sure you have:
12+
13+
- Googled your question.
14+
- Searched open and closed
15+
- Kusion: [GitHub issues](https://github.com/KusionStack/kusion/issues?utf8=%E2%9C%93&q=is%3Aissue)
16+
- kclvm-go: [GitHub issues](https://github.com/KusionStack/kclvm-go/issues?utf8=%E2%9C%93&q=is%3Aissue)
17+
- KCLVM: [GitHub issues](https://github.com/KusionStack/KCLVM/issues?utf8=%E2%9C%93&q=is%3Aissue)
18+
19+
- Read the documentation:
20+
- [Doc](https://kusionstack.io/)
21+
- [Kusion Readme](https://github.com/KusionStack/kusion)
22+
- [kclvm-go Readme](https://github.com/KusionStack/kclvm-go)
23+
- [KCLVM Readme](https://github.com/KusionStack/KCLVM)
24+
25+
-->

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
<!-- Thank you for contributing to KusionStack!
2+
3+
Note:
4+
5+
1. With pull requests:
6+
7+
- Open your pull request against "main"
8+
- Your pull request should have no more than two commits, if not you should squash them.
9+
- It should pass all tests in the available continuous integration systems such as GitHub Actions.
10+
- You should add/modify tests to cover your proposed code changes.
11+
- If your pull request contains a new feature, please document it on the README.
12+
13+
2. Please create an issue first to describe the problem.
14+
15+
We recommend that link the issue with the PR in the following question.
16+
For more info, check https://kusionstack.io/docs/governance/contribute/
17+
-->
18+
19+
#### 1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
20+
21+
- [ ] N
22+
- [ ] Y
23+
24+
<!-- You can add issue references here.
25+
e.g.
26+
fix #123, re #123,
27+
fix https://github.com/XXX/issues/44
28+
-->
29+
30+
#### 2. What is the scope of this PR (e.g. component or file name):
31+
32+
<!-- You can add the scope of this change here.
33+
e.g.
34+
/src/server/core.rs,
35+
kusionstack/KCLVM/kclvm-parser
36+
-->
37+
38+
#### 3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
39+
40+
<!-- You can choose a brief description here -->
41+
- [ ] Affects user behaviors
42+
- [ ] Contains syntax changes
43+
- [ ] Contains variable changes
44+
- [ ] Contains experimental features
45+
- [ ] Performance regression: Consumes more CPU
46+
- [ ] Performance regression: Consumes more Memory
47+
- [ ] Other
48+
49+
<!-- You can add more details here.
50+
e.g.
51+
Call method "XXXX" to ..... in order to ....,
52+
More details: https://XXXX.com/doc......
53+
-->
54+
55+
#### 4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
56+
57+
- [ ] N
58+
- [ ] Y
59+
60+
<!-- You can add more details here.
61+
e.g.
62+
Calling method "XXXX" will cause the "XXXX", "XXXX" modules to be affected.
63+
More details: https://XXXX.com/doc......
64+
-->
65+
66+
#### 5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
67+
68+
<!-- You can choose a brief description here -->
69+
- [ ] Unit test
70+
- [ ] Integration test
71+
- [ ] Benchmark (add benchmark stats below)
72+
- [ ] Manual test (add detailed scripts or steps below)
73+
- [ ] Other
74+
75+
<!-- You can add more details here.
76+
e.g.
77+
The test case in XXXX is used to .....
78+
test cases in /src/tests/XXXXX
79+
test cases https://github.com/XXX/pull/44
80+
benchmark stats: time XXX ms
81+
-->
82+
83+
#### 6. Release note
84+
85+
<!-- compatibility change, improvement, bugfix, and new feature need a release note -->
86+
87+
Please refer to [Release Notes Language Style Guide](https://kusionstack.io/docs/governance/release-policy/) to write a quality release note.
88+
89+
```release-note
90+
None
91+
```

‎.github/README-templates.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# KusionStack GitHub Template files
2+
3+
| File | Description |
4+
|-|-|
5+
| [`bug_report.md`](ISSUE_TEMPLATE/bug-report.md) | GitHub bug issue template. |
6+
| [`enhancement-request.md`](ISSUE_TEMPLATE/enhancement.md) | GitHub enhancement issue template. |
7+
| [`feature_request.md`](ISSUE_TEMPLATE/feature-request.md) | GitHub feature issue template. |
8+
| [`general-question.md`](ISSUE_TEMPLATE/general-question.md) | General Question. |

‎.github/workflows/cla.yml‎

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
name: "CLA Assistant"
2+
on:
3+
issue_comment:
4+
types: [created]
5+
pull_request_target:
6+
types: [opened,closed,synchronize]
7+
8+
jobs:
9+
CLAssistant:
10+
runs-on: ubuntu-latest
11+
steps:
12+
- name: "CLA Assistant"
13+
if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target'
14+
# Beta Release
15+
uses: cla-assistant/github-action@v2.1.3-beta
16+
env:
17+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
18+
# the below token should have repo scope and must be manually added by you in the repository's secret
19+
PERSONAL_ACCESS_TOKEN : ${{ secrets.KUSIONSTACK_BOT_TOKEN }}
20+
with:
21+
path-to-document: 'https://github.com/KusionStack/.github/blob/main/CLA.md' # e.g. a CLA or a DCO document
22+
23+
# branch should not be protected
24+
lock-pullrequest-aftermerge: True
25+
path-to-signatures: 'signatures/version1/cla.json'
26+
remote-organization-name: KusionStack
27+
remote-repository-name: cla.db
28+
branch: 'main'
29+
allowlist: 'test'
30+
31+
#below are the optional inputs - If the optional inputs are not given, then default values will be taken
32+
#remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
33+
#remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
34+
#create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
35+
#signed-commit-message: 'For example: $contributorName has signed the CLA in #$pullRequestNo'
36+
#custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
37+
#custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA'
38+
#custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.'
39+
#lock-pullrequest-aftermerge: false - if you don't want this bot to automatically lock the pull request after merging (default - true)
40+
#use-dco-flag: true - If you are using DCO instead of CLA

‎CLA.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# KusionStack Contributor License Agreement (CLA)
2+
3+
Thank you for your interest in contributing to KusionStack! In order to facilitate collaboration and ensure the proper use of contributions, we require all contributors to sign a Contributor License Agreement (CLA).
4+
5+
KusionStack is a [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/) Sandbox Project and therefore leverages CNCF CLAs. Below you'll find links to both the individual CLA and the corporate CLA defined by the CNCF.
6+
7+
### Individual Contributor License Agreement (ICLA)
8+
9+
If you are contributing to this project as an individual, please review and sign the [Individual Contributor License Agreement (ICLA)](https://github.com/cncf/cla/blob/main/individual-cla.pdf).
10+
11+
### Corporate Contributor License Agreement (CCLA)
12+
13+
If you are contributing on behalf of an organization, please review and sign the [Corporate Contributor License Agreement (CCLA)](https://github.com/cncf/cla/blob/main/corporate-cla.pdf).
14+
15+
## Signing the CLA
16+
17+
You can sign the CLA by posting a Pull Request Comment in the below format:
18+
```
19+
I have read the CLA Document and I hereby sign the CLA
20+
```
21+
22+
## Contact Information
23+
24+
If you have any questions regarding this CLA or the contribution process, please don’t hesitate to reach out to us at [kusionstack@gmail.com](mailto:kusionstack@gmail.com).
25+
26+
Thank you for your contributions and support in making KusionStack better!
27+
28+
---
29+
30+
By contributing to this project, you acknowledge that you have read and agree to abide by the terms of the Contributor License Agreements.

‎CODEOWNERS‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Order in this file is important. Only the last match will be
2+
# used. See https://help.github.com/articles/about-code-owners/

‎CODE_OF_CONDUCT.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# KusionStack Community Code of Conduct
2+
3+
KusionStack follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).

0 commit comments

Comments
 (0)