Chore: Add CONTRIBUTING.md guidelines and standardized templates (#279)

* chore: Improve GitHub workflows, issue template, and gitignore entries

- Add support for manual triggering of build and lint workflows.
- Improve bug report template by clarifying prompts and adding checklist and tips for better explanation of issues.
- Ignore `.md` files in `.github` and `.github/ISSUE_TEMPLATE` folders.
- Add badges for test running and coverage status in README.md.

* chore: Add standardized templates to repository

- Add pull request and feature request templates to the `.github` folder

* docs: Add CONTRIBUTING.md guidelines and update .gitignore.

- Update .gitignore to remove exclusions for browsing history files
- Add an exclusion for CONTRIBUTING.md in the Community section in .gitignore
- Create CONTRIBUTING.md with guidelines for contributors.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,14 +7,34 @@ assignees: ''
 
 ---
 
-**Describe the bug**
-Use `./hack-browser-data -vv` paste result here
+## Describe the bug
+A clear and concise description of what the bug is.
 
+## Log Output
+Please attach or paste the relevant log output. Use `./hack-browser-data -vv` and paste result here.
 
-**Desktop (please complete the following information):**
- - OS Name: 
- - Browser Name:
- - Browser Version:
+## Expected vs Actual Behavior
+Describe what you expected to happen and what actually happened.
 
-**Additional context**
-Add any other context about the problem here.
+## Desktop (please complete the following information):
+Select the operating system(s) you are using:
+- [ ] Windows
+- [ ] macOS
+- [ ] Linux
+
+- OS Version: [e.g. windows 10, macos 10.15.7, ubuntu 20.04]
+- OS Architecture: [e.g. 32-bit, 64-bit]
+- Browser Name: [e.g. chrome, firefox]
+- Browser Version: [e.g. 86.0.4240.111, 82.0.3]
+
+## Additional Details
+- [ ] I ran `hack-browser-data` with administrator/root privileges.
+
+## Checklist
+- [ ] I have checked the [existing issues](https://github.com/moonD4rk/HackBrowserData/issues) for similar problems.
+
+## Screenshots/Videos
+If applicable, add screenshots or videos to help explain your problem.
+
+## Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+## Feature Description
+A clear and concise description of what the feature is.
+
+## Why is this feature needed?
+A clear and concise description of why this feature is needed.
+
+## Checklist
+- [ ] I have checked the [existing issues](https://github.com/moonD4rk/HackBrowserData/issues) for similar problems.
+
+## Screenshots/Videos
+If applicable, add screenshots or videos to help explain your proposal.
+
+## Additional Context
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+## Proposed changes
+
+<!-- Describe the overall picture of your modifications to help maintainers understand the pull request. PRs are required to be associated to their related issue tickets or feature request. -->
+
+
+## Checklist
+
+<!-- Put an "x" in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->
+
+- [ ] Pull request is created against the [dev](https://github.com/moonD4rk/HackBrowserData/tree/dev) branch
+- [ ] All checks passed (lint, unit, build tests etc.) with my changes
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] I have added necessary documentation (if appropriate)

.github/workflows/build.yml

@@ -5,6 +5,7 @@ on:
     branches:
       - main
   pull_request:
+  workflow_dispatch:
 
 jobs:
   build:

.github/workflows/lint.yml

@@ -4,6 +4,7 @@ on:
     branches:
       - main
   pull_request:
+  workflow_dispatch:
 jobs:
   lint:
     name: Lint

.github/workflows/unittest.yml

@@ -1,5 +1,9 @@
 on:
-  [pull_request]
+  pull_request:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
 
 name: run tests
 jobs: