Chrome-Extension
Chrome-Extension copied to clipboard
Different types of Chrome extension
Chrome-Extension
Report Bug · Request Extension
Table of Contents :
- Overview
- Available Extensions
- How to view extension?
- Open Source programs this repo has been part of
- Contribution Guidelines
- Contributors
- Feedback
(Bottom)
Overview
Chrome Extensions are something which we use very frequently in our day-to-day life for example, Grammarly. In this project, similarly, I will be adding some extensions and along with it giving some ideas of extensions that can be implemented. Using extension makes life easier but what if we build an extension— it makes it more exciting. So you may be on any level of learning, you can always contribute to this project and build your very own extensions!
Contribution is fun! ✨
Tech-Stack used :
(Back to top)
Available Extensions
(Back to top)
How to view extension?
Here's an example of what a Chrome Extension usually looks like:
(Image taken from Chrome's extension library as an example.)
Read this documentation it has all the steps.
(Back to top)
Open Source programmes this repo has been part of


(Back to top)
Contribution Guidelines
We would ❤️ for you to contribute to Chrome-Extension and help make it better by adding your ideas or by making current one better! We want contributing to be fun, enjoyable, and educational for everyone. All contributions are welcome, including issues as well as updates.
How to Start? 📌
If you have a idea of any Chrome-Extension you want to build just open an appropriate issue regarding this, we will discuss and assign you that issue. In case you are confused and have queries, just ping me, will help you get along and build!
(Back to top)
Submit a Pull Request 🚀
Branch naming convention is as following
TYPE-ISSUE_ID-DESCRIPTION
When TYPE
can be:
- feat - is a new chrome-extension
- doc - documentation only changes
- fix - a bug fix/improving current extension or UI enhancement
All PRs must include a commit message with the changes description!
For the initial start, fork the project and use git clone command to download the repository to your computer
. A standard procedure for working on an issue would be to:
-
git pull
, before creating a new branch, pull the changes from upstream. Your master needs to be up to date.
$ git pull
- Create new branch from
master
$ git checkout -b [name_of_your_new_branch]
- Work - commit - repeat ( be sure to be in your branch )
(Back to top)
- Push changes to GitHub
$ git push origin [name_of_your_new_branch]
-
Submit your changes for review If you go to your repository on GitHub, you'll see a
Compare & pull request
button. Click on that button. -
Start a Pull Request Now submit the pull request and click on
Create pull request
. -
Get a code review approval/reject
-
After approval, merge your PR
-
GitHub will automatically delete the branch after the merge is done. (they can still be restored).
-
Yey! you made it! 🎊
(Back to top)
Contributors
Thanks to all the people who have contributed 💜
(Back to top)
Code of Conduct
To maintain a safe and inclusive space for everyone to learn and grow, contributors are advised to follow the Code of Conduct.
(Back to top)
Feedback
If you have any feedback or suggestions please reach out to Project - Maintainer.
Or you can create a issue and mention there , which new features or extension can make this Project more good.
(Back to top)