Skip to content

Commit 2256c1b

Browse files
ajay-dhangarajay-dhangar
committed
DSA Repo Initialized for dsa content
0 parents  commit 2256c1b

File tree

1,895 files changed

+321622
-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.

1,895 files changed

+321622
-0
lines changed

‎.deepsource.toml

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
version = 1
2+
3+
[[analyzers]]
4+
name = "javascript"
5+
6+
[analyzers.meta]
7+
plugins = ["react"]
8+
environment = ["nodejs"]

‎.dockerignore

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
node_modules

‎.env.example

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
BASE_URL =
2+
ALGOLIA_API_KEY =
3+
ALGOLIA_APP_ID =
4+
GTM_ID =
5+
GA_ID =

‎.github/CODEOWNERS

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
* @ajay-dhangar

‎.github/FUNDING.yml

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# These are supported funding model platforms
2+
3+
github: Ajay-Dhangar # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
4+
patreon: ajay_dhangar # Replace with a single Patreon username
5+
open_collective: codeharborhub # Replace with a single Open Collective username
6+
ko_fi: # Replace with a single Ko-fi username
7+
tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
8+
community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
9+
liberapay: # Replace with a single Liberapay username
10+
issuehunt: # Replace with a single IssueHunt username
11+
otechie: # Replace with a single Otechie username
12+
lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
13+
custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

‎.github/ISSUE_TEMPLATE/bug_report.yml

+55
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
name: Bug report 🐞
2+
description: File a bug report
3+
title: "[Bug]: "
4+
labels: bug
5+
body:
6+
- type: checkboxes
7+
id: existing-issue
8+
attributes:
9+
label: Is there an existing issue for this?
10+
description: Please search to see if an issue already exists for the bug you encountered.
11+
options:
12+
- label: I have searched the existing issues
13+
required: true
14+
- type: textarea
15+
id: what-happened
16+
attributes:
17+
label: Describe the bug
18+
description: A concise description of what you are experiencing.
19+
placeholder: Tell us what you see!
20+
validations:
21+
required: true
22+
- type: textarea
23+
id: expected-behaviour
24+
attributes:
25+
label: Expected behavior
26+
description: A clear and concise description of what you expected to happen.
27+
validations:
28+
required: true
29+
- type: textarea
30+
id: screenshots
31+
attributes:
32+
label: Add ScreenShots
33+
description: Add sufficient ScreenShots to explain your issue.
34+
- type: dropdown
35+
id: devices
36+
attributes:
37+
label: On which device are you experiencing this bug?
38+
multiple: true
39+
options:
40+
- Android
41+
- iPhone
42+
- Linux
43+
- Chrome
44+
- Windows
45+
- type: checkboxes
46+
id: terms
47+
attributes:
48+
label: Record
49+
options:
50+
- label: "I have read the Contributing Guidelines"
51+
required: true
52+
- label: "I'm a GSSOC'24 contributor"
53+
required: False
54+
- label: "I have starred the repository"
55+
required: true

‎.github/ISSUE_TEMPLATE/config.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
contact_links:
2+
- name: CodeHarborHub Q&A
3+
url: https://codeharborhub.github.io/community/supports#-how-to-get-support
4+
about: Get help from the community with any questions or issues.
5+
6+
- name: CodeHarborHub Features
7+
url: https://codeharborhub.github.io/community/features
8+
about: Explore the features and capabilities of CodeHarborHub.
9+
10+
- name: Meet the Founder or Owner
11+
url: https://codeharborhub.github.io/me/
12+
about: Learn more about the founder and owner of CodeHarborHub.

‎.github/ISSUE_TEMPLATE/documentation.yml

+84
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
name: 📝 Documentation Update
2+
description: Improve Documentation
3+
title: "[Documentation Update]: "
4+
labels: 'enhancement'
5+
body:
6+
- type: checkboxes
7+
id: existing-issue
8+
attributes:
9+
label: Is there an existing issue for this?
10+
description: Please search to see if an issue already exists for the updates you want to make.
11+
options:
12+
- label: I have searched the existing issues
13+
required: true
14+
15+
- type: textarea
16+
id: issue-description
17+
attributes:
18+
label: Issue Description
19+
description: Please provide a clear description of the documentation update you are suggesting.
20+
placeholder: Describe the improvement or correction you'd like to see in the documentation.
21+
validations:
22+
required: true
23+
24+
- type: textarea
25+
id: suggested-change
26+
attributes:
27+
label: Suggested Change
28+
description: Provide details of the proposed change to the documentation.
29+
placeholder: Explain how the documentation should be updated or corrected.
30+
validations:
31+
required: true
32+
33+
- type: textarea
34+
id: rationale
35+
attributes:
36+
label: Rationale
37+
description: Why is this documentation update necessary or beneficial?
38+
placeholder: Explain the importance or reasoning behind the suggested change.
39+
validations:
40+
required: false
41+
42+
- type: dropdown
43+
id: urgency
44+
attributes:
45+
label: Urgency
46+
description: How urgently do you believe this documentation update is needed?
47+
options:
48+
- High
49+
- Medium
50+
- Low
51+
default: 0
52+
validations:
53+
required: true
54+
55+
- type: checkboxes
56+
id: terms
57+
attributes:
58+
label: Acknowledgements
59+
description: Ensure you have read and agree to the project's guidelines.
60+
options:
61+
- label: I have read the Contributing Guidelines
62+
required: true
63+
- label: I'm a GSSOC'24 contributor
64+
required: false
65+
- label: I have starred the repository
66+
required: true
67+
- label: I have read and followed the Contribution Guidelines
68+
required: true
69+
- label: I have followed the code style guidelines of this project
70+
required: true
71+
- label: I have checked for any existing open issues that my pull request may address
72+
required: true
73+
- label: I have ensured that my changes do not break any existing functionality
74+
required: true
75+
- label: Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently
76+
required: true
77+
- label: I have read the resources for guidance listed below
78+
required: true
79+
- label: I have not used AI-generated content (e.g., ChatGPT, other AI tools)
80+
required: true
81+
- label: I have not used content from existing sites (e.g., text, images)
82+
required: true
83+
- label: I have followed all security rules and only shared trusted resources
84+
required: true

‎.github/ISSUE_TEMPLATE/feature_request.yml

+63
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
name: ✨ Feature Request
2+
description: Suggest a feature
3+
title: "[Feature Request]: "
4+
labels: enhancement
5+
body:
6+
- type: checkboxes
7+
id: existing-issue
8+
attributes:
9+
label: Is there an existing issue for this?
10+
description: Please search to see if an issue already exists for this feature.
11+
options:
12+
- label: I have searched the existing issues
13+
required: true
14+
- type: textarea
15+
id: feature-description
16+
attributes:
17+
label: Feature Description
18+
description: Please provide a detailed description of the feature you are requesting.
19+
placeholder: Describe the new feature or enhancement you'd like to see.
20+
validations:
21+
required: true
22+
- type: textarea
23+
id: use-case
24+
attributes:
25+
label: Use Case
26+
description: How would this feature enhance your use of the project?
27+
placeholder: Describe a specific use case or scenario where this feature would be beneficial.
28+
validations:
29+
required: true
30+
- type: textarea
31+
id: benefits
32+
attributes:
33+
label: Benefits
34+
description: What benefits would this feature bring to the project or community?
35+
placeholder: Explain the advantages of implementing this feature.
36+
- type: textarea
37+
id: screenShots
38+
attributes:
39+
label: Add ScreenShots
40+
description: If any...
41+
- type: dropdown
42+
id: priority
43+
attributes:
44+
label: Priority
45+
description: How important is this feature to you?
46+
options:
47+
- High
48+
- Medium
49+
- Low
50+
default: 0
51+
validations:
52+
required: true
53+
- type: checkboxes
54+
id: terms
55+
attributes:
56+
label: Record
57+
options:
58+
- label: "I have read the Contributing Guidelines"
59+
required: true
60+
- label: "I'm a GSSOC'24 contributor"
61+
required: false
62+
- label: "I have starred the repository"
63+
required: true

‎.github/dependabot.yml

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# To get started with Dependabot version updates, you'll need to specify which
2+
# package ecosystems to update and where the package manifests are located.
3+
# Please see the documentation for all configuration options:
4+
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
5+
6+
version: 2
7+
updates:
8+
- package-ecosystem: "npm" # Using npm for Docusaurus
9+
directory: "/"
10+
schedule:
11+
interval: "daily" # Changed to daily from weekly
12+
# open-pull-requests-limit: 0 # Disable version updates for npm dependencies
13+
labels:
14+
- 'pr: dependencies'
15+
16+
- package-ecosystem: "github-actions"
17+
directory: "/"
18+
schedule:
19+
interval: "weekly"
20+
open-pull-requests-limit: 99
21+
labels:
22+
- 'pr: dependencies'
23+
24+
- package-ecosystem: "docker"
25+
directory: "/"
26+
schedule:
27+
interval: "weekly"

‎.github/pull_request_template.md

+86
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
## Related Issue
2+
3+
[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
4+
5+
## Description
6+
7+
[Please include a brief description of the changes or features added]
8+
9+
## Type of PR
10+
11+
- [ ] Bug fix
12+
- [ ] Feature enhancement
13+
- [ ] Documentation update
14+
- [ ] Security enhancement
15+
- [ ] Other (specify): _______________
16+
17+
## Screenshots / Videos (if applicable)
18+
19+
[Attach any relevant screenshots or videos demonstrating the changes]
20+
21+
## Checklist
22+
- [ ] I have performed a self-review of my code.
23+
- [ ] I have read and followed the Contribution Guidelines.
24+
- [ ] I have tested the changes thoroughly before submitting this pull request.
25+
- [ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
26+
- [ ] I have commented my code, particularly in hard-to-understand areas.
27+
- [ ] I have followed the code style guidelines of this project.
28+
- [ ] I have checked for any existing open issues that my pull request may address.
29+
- [ ] I have ensured that my changes do not break any existing functionality.
30+
- [ ] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
31+
- [ ] I have read the resources for guidance listed below.
32+
- [ ] I have followed security best practices in my code changes.
33+
34+
## Additional Context
35+
36+
[Include any additional information or context that might be helpful for reviewers.]
37+
38+
## Resources for Guidance
39+
40+
Please read the following resources before submitting your contribution:
41+
42+
- [ ] [Code Harbor Hub Community Features](https://www.codeharborhub.live/community/features)
43+
- [ ] [Docusaurus Documentation](https://docusaurus.io/docs/create-doc)
44+
- [ ] [React.js Documentation](https://legacy.reactjs.org/docs/getting-started.html)
45+
- [ ] [Markdown Guide](https://www.markdownguide.org/)
46+
- [ ] [MDX Documentation](https://mdxjs.com/docs/)
47+
- [ ] [Mermaid Documentation](https://mermaid.js.org/)
48+
49+
**Resources for DSA Features on Our Site:**
50+
51+
- [ ] [Tabs: Switch Languages](https://www.codeharborhub.live/community/features#multi-language-support-code-blocks)
52+
- [ ] [Line Numbering](https://www.codeharborhub.live/community/features#line-numbering)
53+
- [ ] [Math Equations](https://www.codeharborhub.live/community/features#math-equations-with-katex)
54+
55+
## Contribution Guidelines
56+
57+
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
58+
59+
### Issue Creation
60+
61+
1. **Limit on Issues:**
62+
- Each contributor is allowed to create a maximum of **4 issues per day**. This helps us manage and address issues efficiently.
63+
64+
### Contribution Levels
65+
66+
2. **Basic Contributions:**
67+
- This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
68+
- For these tasks, issues will be assigned the **level1** label.
69+
70+
3. **Acknowledging Hard Work:**
71+
- If a contributor puts in significant effort on a task, the issue will be upgraded to **level2**. This is our way of recognizing and appreciating extra effort.
72+
73+
4. **Feature Additions and Component Work:**
74+
- Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
75+
- The more complex and valuable the contribution, the higher the level assigned.
76+
77+
### Level Definitions
78+
79+
- **Level1:**
80+
- Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.
81+
- **Level2:**
82+
- Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.
83+
- **Level3:**
84+
- Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.
85+
86+
We look forward to your contributions and appreciate your effort in helping us improve the project!

0 commit comments

Comments
 (0)