Skip to content

Commit 11d6a47

Browse files
dauntlessnomaddauntlessnomad
authored
Merge pull request #116 from Kites-Foundation/develop
Main Merge Feb 16 00:25
2 parents 31a9aed + 090e3df commit 11d6a47

File tree

267 files changed

+9892
-1647
lines changed

Some content is hidden

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

267 files changed

+9892
-1647
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
name: "Bug report \U0001F41E"
3+
about: Report something that doesn't work
4+
title: ""
5+
labels: bug
6+
assignees: ""
7+
projects: ""
8+
---
9+
10+
<!--
11+
A Bug is a superset of regressions, but it doesn't have to have worked on One Platform previously. Please provide as much relevant info as possible.
12+
13+
Before opening a new issue, please search existing issues https://github.com/Kites-Foundation/hello-munnar-frontend/issues, https://github.com/Kites-Foundation/hello-munnar-backend
14+
-->
15+
16+
## Describe the bug
17+
18+
<!-- A clear and concise description of what the bug is. -->
19+
20+
## Steps to reproduce
21+
22+
<!--
23+
1. Do '...'
24+
2. Click on '....'
25+
3. See error
26+
27+
For the fastest support, provide a working demo or minimal reproduction using tools such as [codepen](https://codepen.io/) or [jsfiddle](https://jsfiddle.net/)
28+
-->
29+
30+
## Expected behavior
31+
32+
<!-- A clear and concise description of what you expected to happen. -->
33+
34+
## Screenshots
35+
36+
<!-- If applicable, add screenshots to help explain your problem. -->
37+
38+
## Environment
39+
40+
- Operating System(s): Linux/macOS/Windows [Variant and Version]
41+
- Browser: Firefox/Chrome/Safari [Version] / Other (please specify)
42+
- Node Version (please specify)
43+
## Tell us more about your product/project and timeline to help prioritize this issue
44+
45+
<!--
46+
* What product/project does this impact?
47+
* List product/project release(s) and timelines.
48+
* Is this a customer reported blocking issue?
49+
-->

‎.github/ISSUE_TEMPLATE/chore.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
name: "Chore \U0001F527"
3+
about: Internal things, technical debt, and to-do tasks to be performed.
4+
title: ""
5+
labels: chore
6+
assignees: ""
7+
projects: ""
8+
---
9+
10+
<!-- Separate suggestions for updates to configuration or build processes and libraries / Internal things, technical debt, and to-do tasks to be performed should be reported in separate issues.-->
11+
12+
## Is your chore related to a problem? Please describe
13+
14+
<!-- A clear and concise description of what the problem is.-->
15+
16+
## Describe the solution you'd like
17+
18+
<!-- A clear and concise description of what you want to happen. -->
19+
20+
## Describe alternatives you've considered
21+
22+
<!--A clear and concise description of any alternative solutions or features you've considered. -->
23+
24+
## Additional context
25+
26+
<!-- Add any other context or screenshots about the task here. -->

‎.github/ISSUE_TEMPLATE/documentation_proposal.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: "Documentation proposal \U0001F4D6"
3+
about: Propose documentation improvements / additions
4+
title: ""
5+
labels: documentation
6+
assignees: ""
7+
projects: ""
8+
---
9+
10+
<!--For any improvements or additions to existing documentation please be as precise and concise as possible:-->
11+
12+
## Is your suggestion related to code documentation or product documentation problem
13+
14+
<!--
15+
* Code / Product: [e.g. Code, Product]
16+
* File / Document Name: [e.g. README.md, package.json]
17+
-->
18+
19+
## Describe your suggestion
20+
21+
<!-- A clear and concise description of what changes you are proposing. In the case of multiple documents, please create separate issues. -->
22+
23+
## Describe any reference material that might be helpful
24+
25+
<!--
26+
1. Name and description of reference material.
27+
2. Name and description of reference material.
28+
-->
29+
30+
## Additional context
31+
32+
<!-- Add any other context or screenshots about the proposal here. -->

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: "Feature request \U0001F4A1"
3+
about: Suggest an idea for this project
4+
title: ""
5+
labels: enhancement
6+
assignees: ""
7+
projects: ""
8+
---
9+
10+
## Is your feature request related to a problem? Please describe
11+
12+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
13+
14+
## Describe the solution you'd like
15+
16+
<!-- A clear and concise description of what you want to happen. -->
17+
18+
## Describe alternatives you've considered
19+
20+
<!--A clear and concise description of any alternative solutions or features you've considered. -->
21+
22+
## Additional context
23+
24+
<!-- Add any other context or screenshots about the enhancement here. -->

‎.github/ISSUE_TEMPLATE/question.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: "Question \U0001F914"
3+
about: Usage question or discussion about anything related to the platform
4+
title: ""
5+
labels: question
6+
assignees: ""
7+
---
8+
9+
<!--
10+
To make it easier for us to help you, please include as much useful information as possible.
11+
12+
Before opening a new issue, please search existing issues https://github.com/1-Platform/one-platform/issues
13+
-->
14+
15+
## Summary
16+
17+
<!-- Provide a short summary -->
18+
19+
## Relevant information
20+
21+
<!-- Provide as much useful information as you can -->

‎.github/ISSUE_TEMPLATE/regression_report.md‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
name: "Regression report \U0001F570"
3+
about: Tell us about something that worked at one point and now doesn't
4+
title: ""
5+
labels: regression
6+
assignees: ""
7+
---
8+
9+
<!--For regression reports, please provide as much relevant info as possible.-->
10+
11+
## Potential Commit/PR that introduced the regression
12+
13+
<!-- If you have time to investigate, what PR/date introduced this issue. -->
14+
15+
## Describe the regression
16+
17+
<!-- A clear and concise description of what the regression is. -->
18+
19+
## Steps to reproduce
20+
21+
<!--
22+
1. Do '...'
23+
2. Click on '....'
24+
3. See error
25+
26+
For the fastest support, provide a working demo or minimal reproduction using tools such as [codepen](https://codepen.io/) or [jsfiddle](https://jsfiddle.net/)
27+
-->
28+
29+
## Expected behavior
30+
31+
<!-- A clear and concise description of what you expected to happen. -->
32+
33+
## Screenshots
34+
35+
<!-- If applicable, add screenshots to help explain your problem. -->
36+
37+
## Environment
38+
39+
- Operating System(s): Linux/macOS/Windows [Variant and Version]
40+
- Browser: Firefox/Chrome/Safari [Version] / Other (please specify)
41+
42+
## Tell us more about your product/project and timeline to help prioritize this issue
43+
44+
<!--
45+
* What product/project does this impact?
46+
* List product/project release(s) and timelines.
47+
* Is this a customer reported blocking issue?
48+
-->

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
<!--
2+
Follow the steps to create the PR:
3+
4+
Subject: "feat/fix/docs(#issue_id): <PR Subject>"
5+
Assignees: "Kites-hackathon-squad"
6+
-->
7+
8+
# Closes/Fixes/Resolves
9+
10+
### <!-- Any of the keywords: Closes/Fixes/Resolves followed by #issue_id (should be separated by a space only) -->
11+
12+
# Explain the feature/fix
13+
14+
<!-- Provide a clear explaination of the feature/fix implemented -->
15+
16+
## Does this PR introduce a breaking change
17+
18+
<!-- Yes/No -->
19+
20+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
21+
22+
## Screenshots
23+
24+
<!-- If applicable, add screenshots to help explain your problem. -->
25+
26+
<details>
27+
<summary>View Screenshots</summary>
28+
29+
<!-- Add your screenshots below this line -->
30+
31+
</details>
32+
33+
### Ready-for-merge Checklist
34+
35+
- [ ] Expected files: all files in this pull request are related to one feature request or issue (no stragglers)?
36+
- [ ] Does the change have appropriate unit tests?
37+
- [ ] Did tests pass?
38+
- [ ] Did you update or add any necessary documentation (README.md, WHY.md, etc.)?
39+
- [ ] Was this feature demo'd and the design review approved?

‎.github/sonar.yml‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
name: Sonar Scan
2+
on:
3+
push:
4+
branches:
5+
- main
6+
- develop
7+
8+
tags:
9+
- v*
10+
pull_request:
11+
types: [opened, synchronize, reopened]
12+
jobs:
13+
sonarcloud:
14+
name: SonarCloud
15+
runs-on: ubuntu-latest
16+
steps:
17+
- uses: actions/checkout@v2
18+
with:
19+
fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis
20+
- name: SonarCloud Scan
21+
uses: SonarSource/sonarcloud-github-action@master
22+
env:
23+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information, if any
24+
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

‎.gitignore‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@
1717
.env.development.local
1818
.env.test.local
1919
.env.production.local
20+
.eslintcache
2021

2122
npm-debug.log*
2223
yarn-debug.log*

‎.prettierignore‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
src/index.css
2+
.github

0 commit comments

Comments
 (0)