flyingSaucer87 / los-pollos-hermanos

A food-service-based website created with the help of the community
https://flyingsaucer87.github.io/los-pollos-hermanos/
GNU General Public License v3.0
26 stars 100 forks source link
hacktoberfest hacktoberfest2022 html-css

community-website

This is a website building repository where everyone can contribute by adding PRs and solving issues for Hacktoberfest 2022!!

📌Theme:

The theme for this website is a casual food service webpage. Make a website for a local fast food shop.

Note: Tech stack being used: HTML, CSS, JavaScript, Bootstrap.

📌Rules📜:

  1. Don't spam unnecessary PRs and make the hacktoberfest's experience troublesome for others
  2. Contribute to the issues marked for Hacktoberfest. Please refrain from contributing/solving the issues tagged as 'Work in Progress'.
  3. Once you've made your contribution, make sure to add your name to the CONTRIBUTIONS.md file.
  4. Irrelevant, unnecessary and spammy PRs will be deleted.

📌How to Contribute📝:

To contribute, look out for the issues raised by the maintainers as well as the other participants for contributions. Comment down your github ID and tell that you're working on the issue.

To start contributing, follow the below guidelines:

1. Fork this repository.

2. Clone your forked copy of the project.

git clone https://github.com/<your_user_name>/community-website.git

3. Navigate to the project directory :file_folder: .

cd community-website

4. Always take a pull from the upstream repository to your master branch to keep it at par with the main project(updated repository).

git pull upstream main

5. Create a new branch.

git checkout -b <your_branch_name>
try to keep branch name relevant to your contribution, e.g. git checkout -b fix-aboutPagePadding

6. Track your changes:heavy_check_mark: .

git add . 

7. Commit your changes. Use the format described in the Semantic Comments section.

git commit -m "Relevant message"

8. Rebase your branch. This will make sure there are no conflicts with other people's contributions.

git rebase main

9. Push the committed changes in your feature branch to your remote repo.

git push -u origin <your_branch_name>
(you can see your branch name after executing 8th step)

10. To create a pull request, click on compare and pull requests.

11. Add appropriate title and description to your pull request explaining your changes and efforts done.

12. Click on Create Pull Request.

13. Woohoo! You have made a PR to the community-website :boom: . Wait for your submission to be accepted and your PR to be merged.

Semantic Commits

Please use Semantic Commits while you commit your code changes. It helps reviewers to review the code and makes you a better programmer.

feat: (adding new feature)
fix: (bug fix for the user, not a fix to a build script)
docs: (changes to the documentation)
style: (formatting, missing semi colons, etc; no production code change)

Thank you for your interest in contributing to our Repo!🏼

Kudos to you🎈

Best of luck 👍😊

LOOKING FORWARD TO YOUR CONTRIBUTIONS!


### Show some ❤️ by starring⭐ this awesome Repository!

📌Our valuable Contributors👩‍💻👨‍💻 :