Replace personal GitHub token with GitHub App for feedback submission

[devin-ai-integration]

Summary

Replaces Yujong's personal GitHub token (YUJONGLEE_GITHUB_TOKEN_REPO) with a proper GitHub App for creating issues and discussions from the desktop app's feedback feature. This uses @octokit/auth-app for GitHub App authentication which provides better security, automatic token rotation, and isn't tied to a personal account.

Changes:

• Added @octokit/auth-app, @octokit/rest, and @octokit/graphql dependencies
• Replaced single token env var with five GitHub App env vars (using CHARLIE_/CHAR_ prefixes to avoid GitHub's restriction on secrets starting with GITHUB_)
• Bug reports → GitHub Issues with type: "Bug" and product/desktop label
• Feature requests → GitHub Discussions via GraphQL API
• Refactored createGitHubIssue and addCommentToIssue to use Octokit client with App authentication
• Added createGitHubDiscussion function for feature requests

Review & Testing Checklist for Human

• Verify GitHub App permissions: Ensure the app has Issues: Read & write AND Discussions: Read & write permissions
• Verify env vars are set in Fly.io:
  • CHARLIE_APP_ID, CHARLIE_APP_PRIVATE_KEY, CHARLIE_APP_INSTALLATION_ID
  • CHAR_REPO_ID (e.g. R_kgDONa1RRQ)
  • CHAR_DISCUSSION_CATEGORY_ID (e.g. DIC_kwDONa1RRc4CnQnp for Ideas category)
• Test bug report end-to-end: Submit a bug report from desktop app → verify GitHub Issue is created with type: Bug and product/desktop label, and log comment is added
• Test feature request end-to-end: Submit a feature request from desktop app → verify GitHub Discussion is created in the correct category
• Remove old secret: YUJONGLEE_GITHUB_TOKEN_REPO from Fly.io after confirming new flow works

Notes

The env var names use CHARLIE_ and CHAR_ prefixes because GitHub/Infisical rejects secrets starting with GITHUB_.

The type field for issues is supported as of March 2025. Note that Octokit's TypeScript types may not include this field yet, but the API accepts it.

The GraphQL mutation for creating discussions requires the repository node ID and discussion category ID, which can be obtained via:

gh api graphql -f query='
query {
  repository(owner: "fastrepl", name: "hyprnote") {
    id
    discussionCategories(first: 10) {
      nodes { id name }
    }
  }
}'

Requested by @ComputelessComputer

Link to Devin run: https://app.devin.ai/sessions/f98635e6ea4546f581d3a8f5e17b1d21

[netlify]

✅ Deploy Preview for hyprnote canceled.

Name	Link
🔨 Latest commit	e414ab9
🔍 Latest deploy log	https://app.netlify.com/projects/hyprnote/deploys/6982f7e2f0b83a00081eb4dd

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[netlify]

✅ Deploy Preview for hyprnote-storybook canceled.

Name	Link
🔨 Latest commit	e414ab9
🔍 Latest deploy log	https://app.netlify.com/projects/hyprnote-storybook/deploys/6982f7e28039270008512209

[graphite-app]

Invalid parameter type passed to octokit.issues.create(). The GitHub Issues API does not have a type field. This line should be removed.

const response = await octokit.issues.create({
  owner: "fastrepl",
  repo: "hyprnote",
  title,
  body,
  labels,
  // Remove the 'type: issueType,' line
});

The issueType parameter should also be removed from the function signature on line 91 as stated in the PR description.

Spotted by Graphite Agent



Is this helpful? React 👍 or 👎 to let us know.