Merge pull request #113 from hybridmachine/feature-markdown-viewer-plugin

Add MarkdownViewer++ plugin support

Author: hybridmachine

.github/ISSUE_TEMPLATE.md

@@ -17,9 +17,9 @@
 <!--- What actually happened -->
 
 ### Debug Information
-<!--- In your Notepad++, click on the "?" menu (found to the right of "Window" in the menu bar) -->
+<!--- In PaperWasp, click on the "?" menu (found to the right of "Window" in the menu bar) -->
 <!--- In the menu that drops down, choose "Debug Info..." -->
-<!--- A message box will open detailing specifics about your Notepad++ version, plugins, etc. -->
+<!--- A message box will open detailing specifics about your PaperWasp version, plugins, etc. -->
 <!--- CLICK ON THE BUTTON with the text "Copy debug info into clipboard" -->
 <!--- Do a PASTE HERE -->
 

.github/ISSUE_TEMPLATE/1-bug.yml

@@ -16,33 +16,32 @@ body:
       required: true
 - type: checkboxes
   attributes:
-    label: Is the issue reproducible in Notepad++ without plugin?
+    label: Is the issue reproducible in PaperWasp without plugins?
     description: |
-      If feasible, try launching Notepad++ without any plugins.
-      Some updates to Notepad++ modify communication rules used by plugins,
+      If feasible, try launching PaperWasp without any plugins.
+      Some updates to PaperWasp modify communication rules used by plugins,
       and if plugin developers do not keep their plugins in sync with these changes, issues may arise.
       Running without plugins can help diagnose specific problems.
-      You can use cmdline `notepad++.exe -noPlugin`
-      or rename your plugin folder, usually "C:\Program Files\Notepad++\plugins\" to e.g. "...\plugins.bak\").
+      You can temporarily move your user plugin folder, usually `~/Library/Application Support/PaperWasp/plugins`.
     options:
-    - label: I have tried Notepad++ without plugin
+    - label: I have tried PaperWasp without plugins
       required: false
 - type: checkboxes
   attributes:
-    label: Is the issue reproducible in portable version of Notepad++?
+    label: Is the issue reproducible with a clean PaperWasp configuration?
     description: |
-      If feasible, try launching portable version of Notepad++.
-      It can help to diagnose if specific configuration is causing issue.
+      If feasible, try launching PaperWasp with a clean user configuration.
+      It can help diagnose whether a specific configuration is causing the issue.
     options:
-    - label: I have tried portable version of Notepad++
+    - label: I have tried a clean PaperWasp configuration
       required: false
 - type: checkboxes
   attributes:
     label: Does the issue affect SciTE?
     description: |
-      Notepad++ relies on the Lexilla and Scintilla libraries.
+      PaperWasp relies on the Lexilla and Scintilla libraries.
       For more details, visit https://github.com/ScintillaOrg/lexilla and https://sourceforge.net/p/scintilla.
-      Consider using the reference program SciTE to verify whether the issue is a genuine bug in Notepad++.
+      Consider using the reference program SciTE to verify whether the issue is in the shared editor/lexer stack.
       Download Scite from here https://www.scintilla.org/SciTEDownload.html.
     options:
     - label: I have tried SciTE
@@ -84,9 +83,9 @@ body:
   attributes:
     label: Debug Information
     description: |
-      In your Notepad++, click on the "?" menu (found to the right of "Window" in the menu bar).
+      In PaperWasp, click on the "?" menu (found to the right of "Window" in the menu bar).
       In the menu that drops down, choose "Debug Info...".
-      A dialog will open detailing specifics about your Notepad++ version, plugins, etc.
+      A dialog will open detailing specifics about your PaperWasp version, plugins, etc.
       CLICK ON THE BUTTON "Copy debug info into clipboard".
       Do a PASTE HERE
     render: shell

.github/ISSUE_TEMPLATE/2-feature-request.yml

@@ -1,5 +1,5 @@
 name: Feature request
-description: Suggest an idea for Notepad++
+description: Suggest an idea for PaperWasp
 title: "[Feature request] <title>"
 #labels: ["feature"]
 #type: feature
@@ -27,9 +27,9 @@ body:
   attributes:
     label: Debug Information
     description: |
-      In your Notepad++, click on the "?" menu (found to the right of "Window" in the menu bar).
+      In PaperWasp, click on the "?" menu (found to the right of "Window" in the menu bar).
       In the menu that drops down, choose "Debug Info...".
-      A dialog will open detailing specifics about your Notepad++ version, plugins, etc.
+      A dialog will open detailing specifics about your PaperWasp version, plugins, etc.
       CLICK ON THE BUTTON "Copy debug info into clipboard".
       Do a PASTE HERE
     render: shell
@@ -41,12 +41,12 @@ body:
     description: |
       Links? References? Anything that will give us more context about the feature you want!
 
-      Notepad++ relies on the Lexilla and Scintilla libraries.
+      PaperWasp relies on the Lexilla and Scintilla libraries.
       For more details, visit https://github.com/ScintillaOrg/lexilla and https://sourceforge.net/p/scintilla.
       If you have specific language feature requests, consider using the reference program SciTE to verify whether the desired feature is supported.
       You can download SciTE from here https://www.scintilla.org/SciTEDownload.html.
 
-      If you have any questions about Notepad++ usage, explore the community forum https://community.notepad-plus-plus.org/category/7/faq.
+      For upstream Notepad++ usage questions, use the Notepad++ community forum: https://community.notepad-plus-plus.org/category/7/faq.
 
       Tip: You can attach images by clicking this area to highlight it and then dragging files in.
   validations:

.github/workflows/claude-code-review.yml

@@ -0,0 +1,44 @@
+name: Claude Code Review
+
+on:
+  pull_request:
+    types: [opened, synchronize, ready_for_review, reopened]
+    # Optional: Only run on specific file changes
+    # paths:
+    #   - "src/**/*.ts"
+    #   - "src/**/*.tsx"
+    #   - "src/**/*.js"
+    #   - "src/**/*.jsx"
+
+jobs:
+  claude-review:
+    # Optional: Filter by PR author
+    # if: |
+    #   github.event.pull_request.user.login == 'external-contributor' ||
+    #   github.event.pull_request.user.login == 'new-developer' ||
+    #   github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
+
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code Review
+        id: claude-review
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          plugin_marketplaces: 'https://github.com/anthropics/claude-code.git'
+          plugins: 'code-review@claude-code-plugins'
+          prompt: '/code-review:code-review ${{ github.repository }}/pull/${{ github.event.pull_request.number }}'
+          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
+          # or https://code.claude.com/docs/en/cli-reference for available options
+

.github/workflows/claude.yml

@@ -0,0 +1,50 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          # This is an optional setting that allows Claude to read CI results on PRs
+          additional_permissions: |
+            actions: read
+
+          # Optional: Give a custom prompt to Claude. If this is not specified, Claude will perform the instructions specified in the comment that tagged it.
+          # prompt: 'Update the pull request description to include a summary of changes.'
+
+          # Optional: Add claude_args to customize behavior and configuration
+          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
+          # or https://code.claude.com/docs/en/cli-reference for available options
+          # claude_args: '--allowed-tools Bash(gh pr:*)'
+