Skip to content

Latest commit

 

History

History
101 lines (75 loc) · 3 KB

Contributing.md

File metadata and controls

101 lines (75 loc) · 3 KB
Raw

Contributing

Thanks for your interest in contributing to syllabusx.live. We're happy to have you here.

Please take a moment to review this document before submitting your first pull request. We also strongly recommend that you check for open issues and pull requests to see if someone else is working on something similar.

If you need any help, feel free to reach out to @akshat_OwO.

About this repository

Structure

├── src
│  ├── app
│  │  ├── about-us
│  │  ├── changelog
│  │  │  └── [versionId]
│  │  ├── contact-us
│  │  ├── courses
│  │  │  ├── bca
│  │  │  └── btech
│  │  ├── privacy-policy
│  │  ├── t&c
│  ├── components
│  │  ├── modals
│  │  ├── theme
│  │  └── ui
│  ├── hooks
│  ├── layouts
│  ├── lib
│  └── types

Development

Fork this repo

You can fork this repo by clicking the fork button in the top right corner of this page.

Clone on your local machine

git clone https://github.com/your-username/syllabusx-client.git

Navigate to project directory

cd syllabusx-client

Install dependencies

pnpm install

Run development server

pnpm dev

Commit Convention

Before you create a Pull Request, please check whether your commits comply with the commit conventions used in this repository.

When you create a commit we kindly ask you to follow the convention category(scope or module): message in your commit message while using one of the following categories:

  • feat / feature: all changes that introduce completely new code or new features
  • fix: changes that fix a bug (ideally you will additionally reference an issue if present)
  • refactor: any code related change that is not a fix nor a feature
  • docs: changing existing or creating new documentation (i.e. README, docs for usage of a lib or cli usage)
  • build: all changes regarding the build of the software, changes to dependencies or the addition of new dependencies
  • test: all changes regarding tests (adding new tests or changing existing ones)
  • ci: all changes regarding the configuration of continuous integration (i.e. github actions, ci system)
  • chore: all changes to the repository that do not fit into any of the above categories

e.g. docs: create README.md

If you are interested in the detailed specification you can visit https://www.conventionalcommits.org/ or check out the Angular Commit Message Guidelines.

Request for a new feature

If you have a request for a new component, please open a discussion or an issue on GitHub. We'll be happy to help you out.