Skip to content

Commit 668d349

Browse files
ClydeDzClydeDz
committed
Working version of the extension with options page
1 parent 242e60f commit 668d349

32 files changed

Lines changed: 3936 additions & 1 deletion

‎.github/FUNDING.yml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
github: [clydedz]
2+
ko_fi: clydedsouza
3+
custom:
4+
[
5+
"https://sponsor.clydedsouza.net/",
6+
"https://donate.stripe.com/dRmfZggGd02Oa7dejP0kE00",
7+
"https://paypal.me/clydedz",
8+
"https://buymeacoffee.com/clydedsouza",
9+
"https://www.revolut.me/clydedz/",
10+
]

‎.github/ISSUE_TEMPLATE/BUG.yaml‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
name: Bug report
2+
description: Spotted one? Please let me know
3+
title: "[Bug]: "
4+
labels: ["bug", "triage"]
5+
assignees:
6+
- clydedz
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for taking the time to fill out this bug report.
12+
- type: textarea
13+
id: what
14+
attributes:
15+
label: Please explain the issue and what was your expectation
16+
validations:
17+
required: true
18+
- type: textarea
19+
id: how
20+
attributes:
21+
label: Please elaborate the steps to reproduce the issue
22+
validations:
23+
required: true
24+
- type: input
25+
id: browser
26+
attributes:
27+
label: Browser information
28+
placeholder: ex. Chrome version 79.2.1
29+
validations:
30+
required: true
31+
- type: input
32+
id: extension
33+
attributes:
34+
label: Extension version
35+
placeholder: ex. LinkedIn Article Tools 1.0.0
36+
validations:
37+
required: true

‎.github/ISSUE_TEMPLATE/IDEA.yaml‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
name: Submit an idea
2+
description: Submit an idea or feature request
3+
title: "[Idea]: "
4+
labels: ["idea", "triage"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thanks for taking the time to think of an idea or feature and fill out this report.
10+
- type: textarea
11+
id: what
12+
attributes:
13+
label: Please explain your idea/feature request
14+
validations:
15+
required: true
16+
- type: textarea
17+
id: why
18+
attributes:
19+
label: Why would you like to see this incorporated?
20+
validations:
21+
required: true
22+
- type: dropdown
23+
id: selfdevelop
24+
attributes:
25+
label: Do you have capacity to develop this yourself?
26+
options:
27+
- "Yes"
28+
- "No"

‎.github/ISSUE_TEMPLATE/SUPPORT.yaml‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
name: Support
2+
description: Got a question? Pop them here
3+
title: "[Q]: "
4+
labels: ["support"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Please do not use this form to raise issues, bugs, or feature requests.
10+
- type: textarea
11+
id: question
12+
attributes:
13+
label: I want to ask
14+
validations:
15+
required: true
16+
- type: input
17+
id: browser
18+
attributes:
19+
label: Browser information
20+
placeholder: ex. Chrome version 79.2.1
21+
- type: input
22+
id: extension
23+
attributes:
24+
label: Extension version
25+
placeholder: ex. LinkedIn Article Tools 1.0.0

‎.github/pull_request_template.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
## What has changed and why?
2+
3+
(Insert description here)
4+
5+
## Does this fix an open issue?
6+
7+
(If yes, please mention the number here)
8+
9+
## Type of change
10+
11+
- [ ] Bug fix (non-breaking change which fixes an issue)
12+
- [ ] New feature (non-breaking change which adds functionality)
13+
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
14+
15+
## Checklist
16+
17+
- [ ] I have followed the [`CONTRIBUTING` document](https://github.com/ClydeDz/linkedin-article-tools-chrome-extension/blob/main/docs/CONTRIBUTING.md) and have updated the required files.
18+
- [ ] My code follows the code style of this project.
19+
- [ ] All new and existing tests passed.
20+
- [ ] I've manually tested this change locally to ensure no errors appear.

‎.github/workflows/build-deploy.yaml‎

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
name: Build and deploy chrome extension
2+
3+
on:
4+
push:
5+
branches:
6+
- main
7+
paths-ignore:
8+
- "docs/**"
9+
- "*.md"
10+
pull_request:
11+
branches:
12+
- main
13+
paths-ignore:
14+
- "docs/**"
15+
- "*.md"
16+
17+
jobs:
18+
build:
19+
name: Build chrome extension
20+
runs-on: ubuntu-latest
21+
permissions:
22+
checks: write
23+
pull-requests: write
24+
issues: write
25+
statuses: write
26+
contents: write
27+
28+
steps:
29+
- name: Checkout code
30+
uses: actions/checkout@v4
31+
32+
- name: Install Node.js
33+
uses: actions/setup-node@v4
34+
with:
35+
node-version: 20
36+
cache: "npm"
37+
38+
- name: Install NPM packages
39+
run: npm ci
40+
41+
- name: Build project
42+
run: npm run build:prod
43+
44+
- name: Upload extension build files
45+
uses: actions/upload-artifact@v4
46+
with:
47+
name: production-files
48+
path: ./dist
49+
50+
deploy:
51+
name: Deploy chrome extension
52+
needs: build
53+
runs-on: ubuntu-latest
54+
if: github.ref == 'refs/heads/main'
55+
56+
steps:
57+
- name: Download artifact
58+
uses: actions/download-artifact@v4
59+
with:
60+
name: production-files
61+
path: ./dist
62+
63+
- name: Zip contents
64+
uses: montudor/action-zip@v1
65+
with:
66+
args: zip -qq -r extension.zip dist
67+
68+
# - name: Publish to Chrome store
69+
# uses: Klemensas/chrome-extension-upload-action@v1.3
70+
# with:
71+
# refresh-token: ${{ secrets.CHROME_REFRESH_TOKEN }}
72+
# client-id: ${{ secrets.CHROME_CLIENT_ID }}
73+
# client-secret: ${{ secrets.CHROME_CLIENT_SECRET }}
74+
# app-id: ${{ secrets.CHROME_APP_ID }}
75+
# file-name: "./extension.zip"

‎README.md‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,5 @@
1-
# github-unreplied-comments-indicator-chrome-extension
1+
# GitHub Unreplied Comments Indicator
2+
3+
Highlights GitHub pull request comments with no replies, helping you spot unresolved feedback instantly.
4+
5+
This extension helps you stay on top of pull request reviews by visually highlighting GitHub comments that haven’t received a reply. Unreplied comments remain marked until another comment is added to the thread, ensuring you never miss important feedback or leave questions unanswered. Perfect for developers who want to keep PR discussions tidy and ensure all reviewer notes are addressed.

‎babel.config.js‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
module.exports = {
2+
sourceType: "unambiguous",
3+
plugins: ["@babel/plugin-transform-runtime"],
4+
presets: ["@babel/preset-env"]
5+
};

‎docs/CONTRIBUTING.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# Contributing
2+
3+
Contributions are most welcome. I hope this document useful to answer any questions around contributing to this repository.
4+
5+
## Before making any changes
6+
7+
Please open an issue to discuss new ideas or features before going away and developing them. If an idea or feature is deemed unnecessary, your pull request won't be accepted.
8+
9+
## Making changes
10+
11+
- Clone this repo and install the required node modules.
12+
- Run `npm run build` to build this project.
13+
- Follow [these instructions](https://superuser.com/a/247654) to install this extension locally. Use the generated `dist` folder as the folder containing the extensions code to load.
14+
- Once installed, you should see "LinkedIn Article Tools" and four buttons in the bottom of your LinkedIn page. You might need to reload the page to see the changes take effect.
15+
16+
## Merging your changes in
17+
18+
In other words, the pull request process. When you're ready with your changes, open up a pull request to get your changes merged in. Follow the checklist below to ensure you've covered the requirements.
19+
20+
### Checklist
21+
22+
- Think of how you can tackle a piece of work in the smallest unit possible. A small unit, in this case, would be something that adds value even though the changes are small. Small changes are easier to review, hence the request to think small where possible.
23+
- Ensure you've added or updated unit tests. Would your unit test fail if someone was to accidentally modify your code?
24+
- Update the version number in the [manifest.json file](https://github.com/ClydeDz/linkedin-article-tools-chrome-extension/blob/main/src/manifest.json#L5) and [package.json file](https://github.com/ClydeDz/linkedin-article-tools-chrome-extension/blob/main/package.json#L3). We're following the [Semver guide](https://semver.org/), so please check the website to see which number you'd need to increment.
25+
- As a result of your changes, if you need to make changes to screenshots or description of the extension, please let me know in the description of your pull request and we can review your updated copy together. Updating this in the Chrome web store is currently a manual process.
26+
27+
**Note:** Even after a successful build and deployment, the extension still remains in draft/unpublished state in the Chrome developer site. I need to manually submit a version for review which then eventually published the extension.
28+
29+
Thanks!

‎docs/PRIVACY.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Privacy policy
2+
This extension does not handle personal or sensitive user data. No analytics, no cookies, no user information, nothing. Needless to say, no information is shared either.

0 commit comments

Comments
 (0)