-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: post-highlight-page-check #164
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
diivi
approved these changes
Jun 4, 2023
bdougie
approved these changes
Jun 4, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this fix.
github-actions bot
pushed a commit
that referenced
this pull request
Jun 4, 2023
## [1.4.1-beta.2](v1.4.1-beta.1...v1.4.1-beta.2) (2023-06-04) ### π Bug Fixes * post-highlight-page-check ([#164](#164)) ([ed98eb2](ed98eb2))
π This PR is included in version 1.4.1-beta.2 π The release is available on GitHub release Your semantic-release bot π¦π |
github-actions bot
pushed a commit
that referenced
this pull request
Jun 6, 2023
## [1.5.0](v1.4.0...v1.5.0) (2023-06-06) ### π§βπ» Code Refactoring * removed post highlight message passing ([#165](#165)) ([bad2112](bad2112)) ### π Features * extension settings ([#132](#132)) ([722cbbe](722cbbe)) ### π Bug Fixes * highlight redirection, multiple AI generation, draft commit messages ([#163](#163)) ([03b91ab](03b91ab)) * post-highlight-page-check ([#164](#164)) ([ed98eb2](ed98eb2)) * remove configuration enabled check from AI button ([#170](#170)) ([cedca79](cedca79))
π This PR is included in version 1.5.0 π The release is available on GitHub release Your semantic-release bot π¦π |
zer0and1
added a commit
to zer0and1/open-sauced.ai
that referenced
this pull request
Jul 26, 2023
## [1.4.1-beta.2](open-sauced/ai@v1.4.1-beta.1...v1.4.1-beta.2) (2023-06-04) ### π Bug Fixes * post-highlight-page-check ([#164](open-sauced/ai#164)) ([ed98eb2](open-sauced/ai@ed98eb2))
zer0and1
pushed a commit
to zer0and1/open-sauced.ai
that referenced
this pull request
Jul 26, 2023
## [1.5.0](open-sauced/ai@v1.4.0...v1.5.0) (2023-06-06) ### π§βπ» Code Refactoring * removed post highlight message passing ([#165](open-sauced/ai#165)) ([bad2112](open-sauced/ai@bad2112)) ### π Features * extension settings ([#132](open-sauced/ai#132)) ([722cbbe](open-sauced/ai@722cbbe)) ### π Bug Fixes * highlight redirection, multiple AI generation, draft commit messages ([#163](open-sauced/ai#163)) ([03b91ab](open-sauced/ai@03b91ab)) * post-highlight-page-check ([#164](open-sauced/ai#164)) ([ed98eb2](open-sauced/ai@ed98eb2)) * remove configuration enabled check from AI button ([#170](open-sauced/ai#170)) ([cedca79](open-sauced/ai@cedca79))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
This PR adds a check before rendering the "Post a highlight" button on the extension dropdown page, since the feature needs a GitHub PR page to be open for getting PR info using the content-script via message passing. Else a
closed-receiving-end
error arises. 9e0f27b.Additionally, a duplicate
content-scripts.css
file has been deleted and the title, favicon ofindex.html
has been updated. 4ecb35b, adcd315.I'm trying to work out a way to remove the message passing from the post highlight flow completely. Will open a PR if I manage to do so.
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
The error this PR intends to resolve:
Added tests?
Added to documentation?