Skip to content

Commit 197ad36

Browse files
niteshpurohitniteshpurohit
committed
first commit
0 parents  commit 197ad36

42 files changed

Lines changed: 2557 additions & 0 deletions

Some content is hidden

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

‎.github/FUNDING.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
github: [Code-Vedas]

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve
4+
title: "[BUG] Briefly describe the issue"
5+
labels: bug
6+
assignees: ""
7+
---
8+
9+
## Bug Report
10+
11+
### Description
12+
13+
[Provide a clear and concise description of the bug.]
14+
15+
### Steps to Reproduce
16+
17+
1. [First step]
18+
2. [Second step]
19+
3. [Third step]
20+
- [If applicable]
21+
22+
### Expected Behavior
23+
24+
[Describe what you expected to happen.]
25+
26+
### Actual Behavior
27+
28+
[Describe what actually happened.]
29+
30+
### Screenshots or Additional Information
31+
32+
[If applicable, add screenshots or other information to help illustrate the issue.]
33+
34+
### Environment
35+
36+
- Operating System: [e.g., Windows, macOS, Linux]
37+
- Browser (if applicable): [e.g., Chrome, Firefox, Safari]
38+
- Version: [e.g., 1.0.0]
39+
40+
### Checklist
41+
42+
- [ ] I have searched for a similar issue and didn't find any duplicates.
43+
- [ ] I have included all the required information.
44+
- [ ] I have tagged the issue with the label "bug."
45+
46+
<!-- Feel free to add any additional details or context that might be helpful in resolving the issue. -->

‎.github/ISSUE_TEMPLATE/documentation_issue.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
name: Documentation Issue
3+
about: Report an issue with project documentation
4+
title: "[DOCS] Briefly describe the documentation issue"
5+
labels: documentation
6+
assignees: ""
7+
---
8+
9+
## Documentation Issue
10+
11+
### Description
12+
13+
[Provide a clear and concise description of the documentation issue.]
14+
15+
### Affected Documentation
16+
17+
[Specify the affected section(s) or page(s) of the documentation.]
18+
19+
### Suggested Improvement
20+
21+
[If you have a suggestion for improving the documentation, please describe it here.]
22+
23+
### Checklist
24+
25+
- [ ] I have searched for similar documentation issues and found none.
26+
- [ ] I have included all the required information.
27+
- [ ] I have tagged the issue with the label "documentation."
28+
29+
<!-- Feel free to add any additional details that might help in understanding or resolving the documentation issue. -->

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for improvement
4+
title: "[FEATURE] Briefly describe the feature request"
5+
labels: enhancement
6+
assignees: ""
7+
---
8+
9+
## Feature Request
10+
11+
### Description
12+
13+
[Provide a clear and concise description of the feature you're requesting.]
14+
15+
### Use Case
16+
17+
[Explain the use case or scenario where this feature would be beneficial.]
18+
19+
### Proposed Solution
20+
21+
[If you have a specific solution in mind, describe it here.]
22+
23+
### Alternatives Considered
24+
25+
[Have you considered any alternative solutions or workarounds?]
26+
27+
### Additional Context
28+
29+
[Add any additional context or information that might be relevant to the feature request.]
30+
31+
### Checklist
32+
33+
- [ ] I have searched for a similar feature request and didn't find any duplicates.
34+
- [ ] I have included all the required information.
35+
- [ ] I have tagged the issue with the label "enhancement."
36+
37+
<!-- Feel free to add any other details that might help in understanding or implementing the requested feature. -->

‎.github/ISSUE_TEMPLATE/question_or_help.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
name: Question/Help
3+
about: Ask a question or seek help
4+
title: "[QUESTION] Briefly describe your question or issue"
5+
labels: question
6+
assignees: ""
7+
---
8+
9+
## Question/Help
10+
11+
### Description
12+
13+
[Briefly describe the question or issue you need help with.]
14+
15+
### Context
16+
17+
[Provide any relevant context or details that might help others understand your question or issue better.]
18+
19+
### Checklist
20+
21+
- [ ] I have searched for similar questions or issues and found none.
22+
- [ ] I have included all the required information.
23+
- [ ] I have tagged the issue with the label "question."
24+
25+
<!-- Feel free to add any additional details that might help in addressing your question or issue. -->

‎.github/ISSUE_TEMPLATE/report_a_security_vulnerability.md‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
name: Report a security vulnerability
3+
about: Report a security vulnerability to help us improve
4+
title: "[SECURITY] Write a concise title here"
5+
labels: security
6+
assignees: ""
7+
---
8+
9+
<!-- If you believe you have found a security vulnerability in our project, please follow these steps to report it to us. We appreciate your efforts in disclosing the issue responsibly and will work with you to address the problem promptly. -->
10+
11+
# Security Vulnerability Report
12+
13+
## Title
14+
15+
[Concise title describing the vulnerability]
16+
17+
## Contact Information
18+
19+
[Your contact information - email or other preferred means of contact]
20+
[Remember that this information may be publicly visible depending on the project's settings]
21+
22+
## Description
23+
24+
[Detailed description of the vulnerability, including steps to reproduce if possible]
25+
26+
## Supporting Documentation
27+
28+
[Attach any supporting documentation, code, or relevant information]
29+
30+
## Impact
31+
32+
[Describe the impact of the vulnerability]
33+
34+
## Suggestions to Fix
35+
36+
[If you have suggestions on how to fix the vulnerability, please include them here]
37+
38+
## Steps to uncover
39+
40+
[If you have suggestions on how to uncover the vulnerability, please include them here]
41+
42+
## Steps to reproduce
43+
44+
[If you have suggestions on how to reproduce the vulnerability, please include them here]
45+
46+
## Severity
47+
48+
[Low/Medium/High]
49+
50+
## Affected Versions
51+
52+
[List affected versions here]
53+
54+
## Checklist
55+
56+
- [ ] I have filled out all the fields above
57+
- [ ] I have searched for a similar issue in the project and found none
58+
- [ ] I have tagged the issue with the label "security"
59+
- [ ] I understand that I may be contacted for further information and my contact information lies in the issue which may be publicly visible depending on the project's settings
60+
- [ ] I understand and agree to license the code I am providing under the project's license
61+
62+
<!--
63+
After creating the issue, tag it with the label "security". This will notify the project maintainers and we will respond as soon as possible.
64+
65+
Our Response: We will acknowledge your report as soon as possible and provide an estimated timeline for when you can expect a resolution.
66+
67+
Coordination: We will work with you to address the issue, and if necessary, coordinate the release of a fix.
68+
69+
Bounty: We do not offer a bounty for the disclosure of security vulnerabilities for public projects, but we will publicly thank you for your assistance unless you request to remain anonymous. If the project is private, we may offer a bounty at our discretion.
70+
71+
Code and License: The effective license for the code in the project is applied to the code provided by you in the report. If you provide a patch, you agree to license the code under the project's license.
72+
73+
Legal Safe Harbor: We will not take legal action against you or suspend your account if you follow the responsible disclosure process. We appreciate your assistance in helping us maintain the security of our project.
74+
-->

‎.github/ISSUE_TEMPLATE/translations.md‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
name: Translation Issue Report
3+
about: Create a report to help us improve translations
4+
title: "[TRANSLATION] Briefly describe the issue"
5+
labels: translation
6+
assignees: ""
7+
---
8+
9+
# Translation Issue Report
10+
11+
## Description
12+
13+
[Provide a clear and concise description of the translation issue.]
14+
15+
## Context
16+
17+
[Explain the context in which the translation issue occurred.]
18+
19+
## Source Language
20+
21+
[Specify the language of the original content.]
22+
23+
## Target Language
24+
25+
[Specify the language the content was translated into.]
26+
27+
## Incorrect Translation
28+
29+
[Provide the section or phrase that is incorrectly translated.]
30+
31+
## Suggested Translation
32+
33+
[Offer your suggested correction or improvement.]
34+
35+
## Screenshots or Additional Information
36+
37+
[If applicable, add screenshots or other information to help illustrate the translation issue.]
38+
39+
## Environment
40+
41+
- Operating System: [e.g., Windows, macOS, Linux]
42+
- Browser (if applicable): [e.g., Chrome, Firefox, Safari]
43+
- Version: [e.g., 1.0.0]
44+
45+
## Checklist
46+
47+
- [ ] I have searched for similar translation issues and didn't find any duplicates.
48+
- [ ] I have included all the relevant information.
49+
- [ ] I have tagged the issue with the label "translation."
50+
51+
<!-- Feel free to add any additional details or context that might be helpful in addressing the translation issue. -->

‎.github/dependabot.yml‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: bundler
4+
directory: /rails_cron
5+
schedule:
6+
interval: daily
7+
- package-ecosystem: bundler
8+
directory: /docs
9+
schedule:
10+
interval: daily
11+
- package-ecosystem: github-actions
12+
directory: /
13+
schedule:
14+
interval: daily

‎.github/pull_request_template.md‎

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
<!--
2+
The title of the GitHub must follow the following format:
3+
[BUG/DOCS/FEATURE/SECURITY/TRANSLATION] Briefly describe the changes made in this pull request.
4+
5+
If your pull request doesn't fall under any of the above categories, please use the label "OTHER" and describe the changes in the title.
6+
7+
For example:
8+
[FEATURE] Add a new feature to the project
9+
[BUG] Fix bug in the project
10+
[DOCS] Update documentation
11+
[SECURITY] Fix security vulnerability
12+
[TRANSLATION] Translate content into a new language
13+
[OTHER] Briefly describe the changes made in this pull request
14+
15+
A CLA is required for this pull request. Please read and sign the CLA at https://cla.developers.codevedas.com
16+
-->
17+
18+
# Pull Request
19+
20+
## Description
21+
22+
[Provide a clear and concise description of the changes introduced by this pull request.]
23+
24+
## Related Issue
25+
26+
[If your pull request addresses a specific issue, reference it here by linking to the issue using the pound sign (#). For example, #123]
27+
28+
## Proposed Changes
29+
30+
[Outline the changes made in this pull request. Include any new features, bug fixes, or enhancements.]
31+
32+
## Checklist
33+
34+
- [ ] I have tested these changes locally.
35+
- [ ] I have ensured that my code follows the project's coding standards.
36+
- [ ] I have updated the documentation (if applicable).
37+
- [ ] I have added appropriate tests (if applicable).
38+
- [ ] I have updated relevant comments in the code (if applicable).
39+
- [ ] I have confirmed that the changes work with the latest version of dependencies.
40+
- [ ] I have added appropriate labels to the pull request.
41+
42+
## Screenshots or Additional Information
43+
44+
[If applicable, provide screenshots or any additional information that helps reviewers understand the changes.]
45+
46+
## Environment
47+
48+
- Operating System: [e.g., Windows, macOS, Linux]
49+
- Browser (if applicable): [e.g., Chrome, Firefox, Safari]
50+
- Version: [e.g., 1.0.0]
51+
52+
<!-- Feel free to add any additional details or context that might be helpful in reviewing the pull request. -->

0 commit comments

Comments
 (0)