A chrome Extension to save your opened tabs
- https://developer.chrome.com/docs/extensions/mv3/getstarted/
- https://developer.chrome.com/docs/extensions/reference/tabs/
- https://developer.chrome.com/docs/apps/app_storage/
- https://stackoverflow.com/questions/14531102/saving-and-retrieving-from-chrome-storage-sync
- https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/getAllInWindow
- https://developer.chrome.com/docs/extensions/reference/tabs/
- https://www.youtube.com/watch?v=CnkpZR0mRoU&list=PLYxzS__5yYQlWil-vQ-y7NR902ovyq1Xi&index=2
- https://youtu.be/ia_TauKfS1Y?t=122
- setup of the extension in Chrome
- Ui/Ux of the extension, Figma Link.
- Frontend using HTML, CSS.
Refer to the resources above for this part.
Getting started with chrome extensions
chrome.tabs Documentation
- Create/Add workspace
- Store tabs of the workspace in localstorage of chrome. Chrome storage
- Display tabs of the workspace when clicked on the workspace button.
- Delete workspace
- Edit tabs in a workspace.
Mention the part on which you want to work in TabSaverExtension Team
1. Fork this repository.
2. Clone your forked copy of the project.
git clone https://github.com/<your-github-username>/TabSaverExtension.git
3. Add a reference(remote) to the original repository.
git remote add upstream https://github.com/OWASP-STUDENT-CHAPTER/TabSaverExtension.git
4. Check the remotes for this repository.
git remote -v
5. 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
6. Create a new branch.
git checkout -b <your_branch_name>
7. Perfom your desired changes to the code base.
Some code changes
8. Add files
git add .
9. Commit your changes .
git commit -m "Relevant message"
10. Push the committed changes in your feature branch to your remote repo.
git push -u origin <your_branch_name>
11. To create a pull request, click on compare and pull requests. Please ensure you compare your feature branch to the desired branch of the repo you are suppose to make a PR to.
12. Add appropriate title and description to your pull request explaining your changes and efforts done. Always make sure you have pulled the latest code from the main branch before making a PR.
13. Click on Create Pull Request.