Skip to content

Commit 5a86ce9

Browse files
GAURAV906GAURAV906
authored
Merge pull request #5 from LiftOffLLC/develop
Develop
2 parents 08640df + 8639930 commit 5a86ce9

25 files changed

+6607
-305
lines changed

‎.github/ISSUE_TEMPLATE.md‎

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
---
8+
9+
## Description
10+
A clear and concise description of what the bug is.
11+
12+
## Steps to Reproduce
13+
Steps to reproduce the behavior:
14+
1. Go to '...'
15+
2. Click on '....'
16+
3. Scroll down to '....'
17+
4. See error
18+
19+
## Expected Behavior
20+
A clear and concise description of what you expected to happen.
21+
22+
## Actual Behavior
23+
A clear and concise description of what actually happened.
24+
25+
## Environment
26+
- OS: [e.g. macOS, Windows, Linux]
27+
- Node.js Version: [e.g. 14.0.0]
28+
- npm Version: [e.g. 6.14.0]
29+
- Cursor Ops Kit Version: [e.g. 1.2.0]
30+
31+
## Additional Context
32+
Add any other context about the problem here.
33+
34+
## Screenshots
35+
If applicable, add screenshots to help explain your problem.
36+
37+
## Possible Solution
38+
If you have a suggestion for how to fix the issue, please describe it here.
39+
40+
---
41+
name: Feature Request
42+
about: Suggest an idea for this project
43+
title: ''
44+
labels: enhancement
45+
assignees: ''
46+
---
47+
48+
## Description
49+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
50+
51+
## Proposed Solution
52+
A clear and concise description of what you want to happen.
53+
54+
## Alternatives Considered
55+
A clear and concise description of any alternative solutions or features you've considered.
56+
57+
## Additional Context
58+
Add any other context or screenshots about the feature request here.
59+
60+
## Implementation Notes
61+
If you have any thoughts on how this feature could be implemented, please share them here.
62+
63+
---
64+
name: Question
65+
about: Ask a question about the project
66+
title: ''
67+
labels: question
68+
assignees: ''
69+
---
70+
71+
## Question
72+
A clear and concise description of your question.
73+
74+
## Context
75+
Provide any relevant context about your question.
76+
77+
## Research
78+
Describe what you've already tried or researched to find an answer.
79+
80+
## Additional Information
81+
Add any other information that might be helpful in answering your question.

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
## Description
2+
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
3+
4+
Fixes # (issue)
5+
6+
## Type of Change
7+
Please delete options that are not relevant.
8+
9+
- [ ] Bug fix (non-breaking change which fixes an issue)
10+
- [ ] New feature (non-breaking change which adds functionality)
11+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
12+
- [ ] This change requires a documentation update
13+
14+
## How Has This Been Tested?
15+
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
16+
17+
- [ ] Test A
18+
- [ ] Test B
19+
20+
## Checklist:
21+
- [ ] My code follows the style guidelines of this project
22+
- [ ] I have performed a self-review of my own code
23+
- [ ] I have commented my code, particularly in hard-to-understand areas
24+
- [ ] I have made corresponding changes to the documentation
25+
- [ ] My changes generate no new warnings
26+
- [ ] I have added tests that prove my fix is effective or that my feature works
27+
- [ ] New and existing unit tests pass locally with my changes
28+
- [ ] Any dependent changes have been merged and published in downstream modules
29+
30+
## Screenshots (if appropriate):
31+
32+
## Additional Context
33+
Add any other context about the pull request here.

‎.github/workflows/ci.yml‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
name: CI
2+
3+
on:
4+
push:
5+
branches: [ main, develop ]
6+
pull_request:
7+
branches: [ main, develop ]
8+
9+
jobs:
10+
test:
11+
runs-on: ubuntu-latest
12+
13+
steps:
14+
- uses: actions/checkout@v2
15+
- name: Use Node.js 18.x
16+
uses: actions/setup-node@v2
17+
with:
18+
node-version: '18.x'
19+
cache: 'npm'
20+
- name: Install dependencies
21+
run: npm ci
22+
- name: Run linting
23+
run: npm run lint

‎.gitignore‎

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Dependencies
22
node_modules/
3-
package-lock.json
43
yarn.lock
54
pnpm-lock.yaml
65

@@ -55,6 +54,17 @@ coverage/
5554
ehthumbs.db
5655
Thumbs.db
5756

57+
# Infrastructure
58+
.terraform/
59+
*.tfstate
60+
*.tfstate.*
61+
*.tfvars
62+
.terraform.lock.hcl
63+
*.tfplan
64+
*.tfplan.json
65+
aws-credentials.json
66+
~/.aws/
67+
5868
# Misc
5969
*.pid
6070
*.seed

‎CHANGELOG.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Changelog
2+
3+
All notable changes to this project will be documented in this file.
4+
5+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7+
8+
## [1.1.0] - 2024-03-12
9+
10+
### Added
11+
- Initial open source release
12+
- Support for multiple roles (frontend, backend, infra, devops)
13+
- Role-specific rules and configurations
14+
- CI/CD workflows for GitHub Actions
15+
- Husky pre-commit hooks
16+
- Comprehensive documentation
17+
18+
### Changed
19+
- Improved error handling and logging
20+
- Enhanced configuration management
21+
- Optimized file copying and backup processes
22+
23+
### Fixed
24+
- Fixed MDC file handling during package preparation
25+
- Resolved version management issues
26+
- Addressed configuration validation bugs
27+
28+
## [1.0.0] - 2024-03-01
29+
30+
### Added
31+
- Initial release
32+
- Basic role support
33+
- Configuration management
34+
- File backup and restore functionality
35+
- Basic validation and error handling
36+
37+
[1.1.0]: https://github.com/LiftOffLLC/cursor-ops-kit/compare/v1.0.0...v1.1.0
38+
[1.0.0]: https://github.com/LiftOffLLC/cursor-ops-kit/releases/tag/v1.0.0

‎CODE_OF_CONDUCT.md‎

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
[INSERT CONTACT METHOD].
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

0 commit comments

Comments
 (0)