Leave-Application-Portal

Leave application portal for IIIT-A to speed up leave approval process

Installation

1. install [xampp] (https://www.apachefriends.org/download.html)
2. Go to xampp/htdocs
3. git clone (your repo link)
4. start localhost server and run the server, also run the sql database
5. Go to localhost/phpmyadmin and run sqlcode command provided in repository in sql terminal
6. You are ready to go! just type localhost/{your folder name in /htdocs} in url

Requirements

Basic Git and Github. (Feel free to contact any mentor if you have any issue regarding Git and Github.)

Contributing

1. Fork the project
2. In gitbash or terminal, use the following commands - 2.1 git clone {url of the forked repo (the one in your account)} 2.2 git remote add original {url of original repo.} (You can use this remote to sync your repo with the original project) Syncing a fork
3. After you have solved the issue in your local system, you need to commit the changes, push them to your repository, and send a pull request. Making changes and commits [Pull Request] (https://help.github.com/articles/about-pull-requests/)

Claim an issue

To claim an issue please comment on the issue as @opencodebot claim and the bot will assign you the issue.

making pr to this project

1. please mention issue number in description while making pr (e.g. #23) and changes made
2. if you solve only part of an issue mention the part you solved in changes.
3. Provide the relevant screenshot for easier review.

Guidelines

Please help us follow the best practice to make it easy for the reviewer as well as the contributor. We want to focus on the code quality more than on managing pull request ethics.

1. People before code: If any of the following rules are violated, the pull-requests must not be rejected. This is to create an easy and joyful onboarding process for new programmers and first-time contributors.

2. Single commit per pull request and name the commit as something meaningful, example: Adding <-your-name-> in students/mentors section.

3. Reference the issue numbers in the commit message if it resolves an open issue. Follow the pattern Fixes #

4 .Provide the link to live gh-pages from your forked repository or relevant screenshot for easier review.

5 .Pull Request older than 3 days with no response from the contributor shall be marked closed.

6 .Do not make PR which is not related to any issues. You can create an issue and solve it once we approve them.

7 .Avoid duplicate PRs, if need be comment on the older PR with the PR number of the follow-up (new PR) and close the obsolete PR yourself.

8 .Be polite: Be polite to other community members.

Communicate: Whether you are working on a new feature or facing a doubt please feel free to ask us on our slack channel. We will be happy to help you out.