[{"content":"Installation #Download Issuenator from the Mac App Store.\nRequirements # macOS 14.0 (Sonoma) or later A GitHub account A GitHub personal access token Setting Up Your API Key #Issuenator uses the GitHub GraphQL API to fetch issues from your repositories. You\u0026rsquo;ll need to create a personal access token:\nCreating a Fine-Grained Token (Recommended) # Go to GitHub Settings \u0026gt; Developer settings \u0026gt; Personal access tokens \u0026gt; Fine-grained tokens Click \u0026ldquo;Generate new token\u0026rdquo; Give it a descriptive name like \u0026ldquo;Issuenator\u0026rdquo; Set an expiration Under \u0026ldquo;Repository access\u0026rdquo;, choose which repos to grant access Under \u0026ldquo;Permissions \u0026gt; Repository permissions\u0026rdquo;, enable: Issues: Read-only Metadata: Read-only Pull requests: Read-only (for linked PR information) Under \u0026ldquo;Permissions \u0026gt; Account permissions\u0026rdquo;, enable: Profile: Read and write (for your username and avatar). We only need read permission, but GitHub doesn\u0026rsquo;t expose read-only for Profile. Click \u0026ldquo;Generate token\u0026rdquo; and copy it Creating a Classic Token # Go to GitHub Settings \u0026gt; Developer settings \u0026gt; Personal access tokens \u0026gt; Tokens (classic) Click \u0026ldquo;Generate new token (classic)\u0026rdquo; Give it a descriptive name Set an expiration Select scopes: repo user Click \u0026ldquo;Generate token\u0026rdquo; and copy it Adding the Token to Issuenator # Open Issuenator You\u0026rsquo;ll be prompted to enter your API key on first launch Paste your token and click Save The token is stored securely in your macOS Keychain Adding Your First Repository #Once your API key is configured:\nEnter the full GitHub URL (e.g., https://github.com/apple/swift) Choose a color for the repository label Optionally customize fetch frequency and archive settings Click Add Repository Issuenator will fetch all open issues from the repository. Depending on the repository size, this may take a moment.\nAdding More Repositories #After initial setup, use Cmd+Ctrl+A or Repositories → Add Repository to add more repos.\nAdd One at a Time # On the Add One tab, enter the full GitHub URL (e.g., https://github.com/apple/swift) Optionally set a custom display name Choose a color for the repository Click Add Repository Add Multiple Repositories #Need to add several repos at once? Use bulk import:\nSelect the Add Many tab Enter full repository URLs, one per line: https://github.com/apple/swift https://github.com/facebook/react https://github.com/microsoft/vscode Click Add Repositories Colors are automatically assigned to each repository. Issuenator will validate each URL and fetch all open issues.\nNext Steps # Learn about the different Dashboards and how to use them Set up Filters \u0026amp; Tags to organize issues automatically Customize Settings to match your workflow ","date":null,"permalink":"/docs/getting-started/","section":"Documentation","summary":"Installation #Download Issuenator from the Mac App Store.\nRequirements # macOS 14.0 (Sonoma) or later A GitHub account A GitHub personal access token Setting Up Your API Key #Issuenator uses the GitHub GraphQL API to fetch issues from your repositories.","title":"Getting Started"},{"content":"Issuenator organizes your issues into purpose-built dashboards. Each dashboard shows a different slice of your issues based on their state and your relationship to them.\nTriage Dashboards #Inbox #Your starting point. The Inbox contains:\nNew issues created on repositories you watch Issues with updates that need your attention Triage issues from your Inbox by:\nWatching them to track ongoing progress Ignoring them to dismiss from your attention Leaving them to auto-archive when closed Assigned #Issues assigned to you across all repositories. This dashboard is hidden when empty.\nTracking Dashboards #Watching #Issues you\u0026rsquo;ve explicitly chosen to track. Add issues here when you want to follow their progress but they\u0026rsquo;re not assigned to you.\nMy Issues #Issues you authored. These are automatically tracked so you never lose sight of bugs you reported or features you requested.\nTagged #A cross-repository view of issues organized by your custom tags. Filter by specific tags to see related issues across all your repos.\nBackground Dashboards #Inactive #Open issues that haven\u0026rsquo;t had activity for a configurable number of days. Issues automatically move here when they go stale, and automatically return to their original dashboard when activity resumes.\nIgnored #Issues you\u0026rsquo;ve dismissed. They won\u0026rsquo;t appear in other dashboards but remain accessible here. If you\u0026rsquo;re @mentioned on an ignored issue, it will automatically un-ignore.\nArchived #Closed issues that have passed the archive retention window. Kept for reference but out of your active workflow.\nRepository Views #Expand the Repositories section in the sidebar to see per-repository views. Each shows a badge count of issues with updates.\nSorting and Filtering #Every dashboard supports:\nSorting by last updated, created date, comments, reactions, state, or title Filtering by repository, labels, state, and \u0026ldquo;has updates\u0026rdquo; Search across issue titles and body text Filter chips showing active filters with one-click removal Sort preferences are saved per-dashboard.\nSearch #Press Cmd+F to focus the search field and find issues by title or body text.\nSearch Scope\nBy default, search filters the current dashboard. Toggle the scope button to search across all issues in all dashboards—useful when you\u0026rsquo;re not sure where an issue landed.\n","date":null,"permalink":"/docs/dashboards/","section":"Documentation","summary":"Issuenator organizes your issues into purpose-built dashboards. Each dashboard shows a different slice of your issues based on their state and your relationship to them.\nTriage Dashboards #Inbox #Your starting point.","title":"Dashboards"},{"content":"Custom Tags #Tags are your personal organization system. Unlike GitHub labels, tags:\nStay completely local on your Mac Never sync to GitHub Work across all repositories Can be applied manually or automatically Creating Tags # Open Tags from the menu (Cmd+Ctrl+T) Click New Tag Enter a name and choose from 8 pastel colors Click Save Applying Tags #Manually:\nIn issue detail view, click the Tag button Right-click an issue card and select from your tags Automatically:\nCreate an automatic filter with a \u0026ldquo;Apply tag\u0026rdquo; action Viewing Tagged Issues #The Tagged dashboard shows all tagged issues across repositories. Use the filter to view specific tags.\nAutomatic Filters #Automatic filters categorize incoming issues based on rules you define. When issues are fetched, matching filters apply their actions automatically.\nCreating a Filter # Open Filters from the menu (Ctrl+F) Click New Filter Define your conditions and action Click Save Filter Conditions #Build conditions using:\nField Description Author GitHub username of issue creator Title Issue title text Body Issue description text Repository Repository name Label GitHub label name Operators # Operator Description Equals Exact match Includes Contains the text Does not equal Exact non-match Does not include Does not contain the text Condition Logic #Combine multiple conditions with:\nAny of - Matches if any condition is true (OR) All of - Matches only if all conditions are true (AND) None of - Matches only if no conditions are true (NOR) Filter Actions #When an issue matches a filter:\nAction Effect Ignore Move to Ignored dashboard Watch Move to Watching dashboard Apply tag Add a specific tag Flag important Mark as important Examples #Ignore bot-created issues:\nCondition: Author includes \u0026ldquo;bot\u0026rdquo; Action: Ignore Tag security issues:\nCondition: Label equals \u0026ldquo;security\u0026rdquo; Action: Apply tag \u0026ldquo;Security\u0026rdquo; Watch issues mentioning your project:\nCondition: Body includes \u0026ldquo;my-project-name\u0026rdquo; Action: Watch Filter Evaluation # All matching filters apply (they compose, not compete) Filters run when issues are fetched Existing issues aren\u0026rsquo;t retroactively filtered ","date":null,"permalink":"/docs/filters-tags/","section":"Documentation","summary":"Custom Tags #Tags are your personal organization system. Unlike GitHub labels, tags:\nStay completely local on your Mac Never sync to GitHub Work across all repositories Can be applied manually or automatically Creating Tags # Open Tags from the menu (Cmd+Ctrl+T) Click New Tag Enter a name and choose from 8 pastel colors Click Save Applying Tags #Manually:","title":"Filters \u0026 Tags"},{"content":"Access Settings via Cmd+, or from the application menu.\nGlobal Settings #Default Dashboard #Choose which dashboard opens when you launch Issuenator.\nInactive Threshold #Number of days without activity before an issue moves to the Inactive dashboard. Issues automatically return when they receive new activity.\nDefault: 14 days\nArchive Timing #How long after an issue closes before it moves to Archived. Different dashboards have different default behaviors:\nDashboard Default Behavior My Issues Archive only on acknowledgment Watching Configurable delay Assigned Configurable delay Inbox Configurable delay after closure Ignored Immediately on closure Fetch Frequency #How often Issuenator automatically fetches new issues from GitHub.\nOption Description Several times per hour Most frequent updates Hourly (default) Balanced freshness and API usage Several times per day Reduced API calls Daily Minimal API usage Display Options # Show/hide specific dashboards in the sidebar Configure issue card information density Label display preferences Per-Repository Settings #Override global settings for individual repositories:\nCustom Name \u0026amp; Color #Give repositories display names and colors for visual recognition in the issue list.\nArchive Override #Set a custom archive delay for this repository\u0026rsquo;s issues.\nInactive Override #Set a custom inactive threshold for this repository.\nFetch Frequency Override #Fetch this repository more or less frequently than the global default.\nAPI Key Management #Viewing Token Status #See when your token expires (if expiration was set).\nUpdating Your Token # Go to Settings \u0026gt; API Key Enter your new token Click Save The new token is validated before saving. Your old token is replaced in Keychain.\nKeyboard Shortcuts #Navigation # Shortcut Action Cmd+1 Go to Inbox Cmd+2 Go to Watching Cmd+3 Go to My Issues Cmd+4 Go to Assigned Cmd+5 Go to Inactive Cmd+6 Go to Ignored Cmd+7 Go to Tagged Cmd+8 Go to Archived Cmd+F Focus Search Issues # Shortcut Action Cmd+B Toggle Bulk Operations T Apply Tags to Selected Issue Cmd+Ctrl+W Watch an Issue by URL Repositories # Shortcut Action Cmd+Ctrl+A Add Repository Cmd+Ctrl+M Manage Repositories Tags # Shortcut Action Cmd+Ctrl+T Create Tag Cmd+Ctrl+G Manage Tags Filters # Shortcut Action Ctrl+F Create Filter Ctrl+M Manage Filters App # Shortcut Action Cmd+, Open Settings Cmd+K Manage API Key Cmd+L View Logs Cmd+D View Documentation Activity Logs #Issuenator keeps a log of app activity during each session—useful for troubleshooting or understanding what happened during a fetch.\nViewing Logs\nPress Cmd+L or choose Logs → View Logs Logs show fetch operations, errors, and app events Logs are kept in memory only and cleared when you quit the app You can export logs to a file for support requests ","date":null,"permalink":"/docs/settings/","section":"Documentation","summary":"Access Settings via Cmd+, or from the application menu.\nGlobal Settings #Default Dashboard #Choose which dashboard opens when you launch Issuenator.\nInactive Threshold #Number of days without activity before an issue moves to the Inactive dashboard.","title":"Settings"},{"content":"Issuenator requires a GitHub personal access token to fetch issues from your repositories.\nToken Types #GitHub offers two types of personal access tokens:\nFine-Grained Tokens (Recommended) #Fine-grained tokens offer more precise control over permissions and repository access.\nRequired Repository Permissions:\nPermission Access Level Purpose Issues Read-only Fetch issue data Metadata Read-only Repository information Pull requests Read-only Linked PR information Required Account Permissions:\nPermission Access Level Purpose Profile Read and write Username and avatar to identify your issues Repository Access:\nChoose between:\nAll repositories - Token works with any repo you have access to Selected repositories - Explicitly choose which repos the token can access Classic Tokens #Classic tokens use broader OAuth scopes.\nRequired Scopes:\nScope Purpose repo Read permissions for any repository you want to watch user Username and avatar for profile and to find \u0026ldquo;my\u0026rdquo; issues Creating Your Token #Fine-Grained Token # Go to GitHub Settings \u0026gt; Developer settings \u0026gt; Fine-grained tokens Click Generate new token Set a name: \u0026ldquo;Issuenator\u0026rdquo; Set expiration (recommended: 90 days or custom) Choose repository access Under Repository permissions, set Issues, Metadata, and Pull requests to Read-only Under Account permissions, set Profile to read and write Click Generate token Copy the token immediately - you won\u0026rsquo;t see it again Classic Token # Go to GitHub Settings \u0026gt; Developer settings \u0026gt; Tokens (classic) Click Generate new token (classic) Set a name: \u0026ldquo;Issuenator\u0026rdquo; Set expiration Check repo and user scopes Click Generate token Copy the token immediately Token Storage #Your token is stored securely in the macOS Keychain:\nEncrypted at rest Protected by your macOS login Accessible only to Issuenator Never sent anywhere except GitHub\u0026rsquo;s API Token Expiration #If you set an expiration date:\nIssuenator shows the expiration date in Settings Create a new token before expiration Update the token in Settings \u0026gt; API Key Troubleshooting #\u0026ldquo;Bad credentials\u0026rdquo; Error # Token may have expired Token may have been revoked Check GitHub token settings for status Missing Private Repositories # Fine-grained tokens: Add the repository to \u0026ldquo;Selected repositories\u0026rdquo; Classic tokens: Ensure repo scope is enabled SAML SSO Organizations #If your organization uses SAML SSO:\nCreate the token normally Go to GitHub token settings Click Configure SSO next to your token Authorize for each organization that requires it ","date":null,"permalink":"/docs/api-key/","section":"Documentation","summary":"Issuenator requires a GitHub personal access token to fetch issues from your repositories.\nToken Types #GitHub offers two types of personal access tokens:\nFine-Grained Tokens (Recommended) #Fine-grained tokens offer more precise control over permissions and repository access.","title":"API Key Setup"},{"content":"Version 1.0 #Coming soon\nInitial release of Issuenator.\nFeatures # Smart Dashboards: Inbox, Watching, My Issues, Assigned, Inactive, Ignored, Tagged, Archived Visual Issue Cards: Repository colors, comment counts, update indicators, labels Issue Detail View: Full metadata, linked PRs, comments with reactions Custom Tags: Private, local-only tags with 8 color options Automatic Filters: Rule-based issue categorization Bulk Operations: Select multiple issues and act on them at once Background Sync: Configurable automatic fetching (hourly by default) Per-Repository Settings: Custom names, colors, and behavior overrides Keyboard Shortcuts: Full keyboard navigation including Cmd+1-8 for dashboards Native macOS: Built with SwiftUI for optimal performance and accessibility ","date":null,"permalink":"/docs/release-notes/","section":"Documentation","summary":"Version 1.0 #Coming soon\nInitial release of Issuenator.\nFeatures # Smart Dashboards: Inbox, Watching, My Issues, Assigned, Inactive, Ignored, Tagged, Archived Visual Issue Cards: Repository colors, comment counts, update indicators, labels Issue Detail View: Full metadata, linked PRs, comments with reactions Custom Tags: Private, local-only tags with 8 color options Automatic Filters: Rule-based issue categorization Bulk Operations: Select multiple issues and act on them at once Background Sync: Configurable automatic fetching (hourly by default) Per-Repository Settings: Custom names, colors, and behavior overrides Keyboard Shortcuts: Full keyboard navigation including Cmd+1-8 for dashboards Native macOS: Built with SwiftUI for optimal performance and accessibility ","title":"Release Notes"},{"content":"Welcome to the Issuenator documentation. Here you\u0026rsquo;ll find guides for getting started and making the most of the app.\nGetting Started #New to Issuenator? Start here:\nInstallation \u0026amp; Setup - Download, install, and configure your GitHub API key Adding Repositories - Start tracking issues from your repos Core Concepts # Dashboards - Understanding the different views Filters \u0026amp; Tags - Organizing issues automatically and manually Settings - Configuring Issuenator to work your way Reference # API Key Setup - GitHub token permissions and configuration Release Notes - What\u0026rsquo;s new in each version ","date":null,"permalink":"/docs/","section":"Documentation","summary":"Welcome to the Issuenator documentation. Here you\u0026rsquo;ll find guides for getting started and making the most of the app.\nGetting Started #New to Issuenator? Start here:\nInstallation \u0026amp; Setup - Download, install, and configure your GitHub API key Adding Repositories - Start tracking issues from your repos Core Concepts # Dashboards - Understanding the different views Filters \u0026amp; Tags - Organizing issues automatically and manually Settings - Configuring Issuenator to work your way Reference # API Key Setup - GitHub token permissions and configuration Release Notes - What\u0026rsquo;s new in each version ","title":"Documentation"},{"content":"A Dedicated Issue Tracker for Maintainers #Issuenator is built specifically for open source maintainers who need to track issues across multiple repositories without drowning in GitHub notifications.\nSmart Dashboards #Issuenator organizes your issues into purpose-built dashboards:\nInbox - New issues on your repos plus issues with updates that need triage Watching - Issues you\u0026rsquo;ve explicitly chosen to keep an eye on My Issues - Issues you authored, automatically tracked Assigned - Issues assigned to you (hidden when empty) Inactive - Open issues with no activity for a configurable number of days Ignored - Issues you\u0026rsquo;ve dismissed from your attention Tagged - Cross-repository view filtered by your custom tags Archived - Closed issues kept for reference Per-Repository - Filter any dashboard to a single repo, or view a dedicated repo-specific dashboard Visual Scanning #Designed for quick triage, not endless reading:\nRepository color bars for instant recognition Bold comment counts when there are new comments Background color shifts for issues with updates \u0026ldquo;New\u0026rdquo; badges on freshly created issues GitHub label colors preserved Author avatars and assignee display Issue Details #When you need to dive deeper:\nFull issue metadata (author, assignees, labels, milestone, reactions) Linked Pull Requests with their current state Markdown-rendered description Complete comment thread with reactions Collapsible already-viewed comments Quick actions: Watch, Ignore, Flag, Tag Private Tags #Organize issues your way without touching GitHub:\nCreate custom tags with 8 color options Apply tags manually or automatically via filters Tags stay completely local - never synced to GitHub View all tagged issues across repos in one place Visually distinct from GitHub labels Use Cases\nTag issues from specific authors as VIP Privately tag \u0026ldquo;Won\u0026rsquo;t Do\u0026rdquo; where you can\u0026rsquo;t publicly say that for Reasons Tag issues related to specific features to get a view of how features impact work across repositories Automatic Filters #Set up rules to categorize incoming issues:\nFilter by author, title, body text, repository, or labels Actions: Ignore, Watch, Apply tag, Flag as important Combine multiple conditions with Any/All/None logic Rules apply automatically when issues are fetched Bulk Operations #When you need to process many issues at once, bulk operations mode lets you work efficiently.\nHow It Works\nPress Cmd+B to enter bulk operations mode Click issues to select them (selection count displays in the toolbar) Choose an action: Tag, Archive, Watch, Ignore, or Flag All selected issues are updated at once Use Cases\nTag all issues related to a release Archive a batch of resolved issues Ignore a flood of bot-generated issues Watch all issues from a new contributor Bulk operations respect dashboard context. You\u0026rsquo;ll only see actions that make sense for the current view.\nSmart Lifecycle Management #Issues move through your dashboards intelligently:\nConfigurable inactive threshold (issues with no activity) Relationship-based archive timing (different rules for each dashboard) Auto-reactivation when inactive issues get new activity @mentions automatically un-ignore ignored issues Background Sync #Stay up to date without manual refreshing:\nAutomatic fetching at configurable intervals Per-repository frequency overrides Manual fetch available anytime Efficient incremental updates via GitHub GraphQL API Per-Repository Settings #Customize behavior for each repo:\nCustom display names and colors Override archive and inactive thresholds Adjust fetch frequency Configure label display priority Native macOS Experience #Issuenator is built specifically for Mac using Apple\u0026rsquo;s SwiftUI framework, not a web app wrapped in Electron.\nWhat This Means for You\nFast, responsive interface that feels like a native Mac app Respects your system preferences (light mode, dark mode, accent colors) Full VoiceOver and accessibility support Efficient memory and battery usage Works offline with locally stored data No Subscription, No Account #Unlike many developer tools, Issuenator is a one-time purchase with no recurring fees. You don\u0026rsquo;t need to create an Issuenator account. Just add your GitHub token and start organizing.\nBuy once, own forever No account registration required No usage limits or feature tiers All your data stays on your Mac ","date":null,"permalink":"/features/","section":"Issuenator","summary":"A Dedicated Issue Tracker for Maintainers #Issuenator is built specifically for open source maintainers who need to track issues across multiple repositories without drowning in GitHub notifications.\nSmart Dashboards #Issuenator organizes your issues into purpose-built dashboards:","title":"Features"},{"content":"","date":null,"permalink":"/","section":"Issuenator","summary":"","title":"Issuenator"},{"content":"Privacy Policy #Last updated: January 2026\nOverview #Issuenator is a macOS app written by Dachary Carey.\nThe Issuenator website is designed to provide information about the Issuenator app for users who may be interested in its functionality.\nThe privacy policy detailed herein applies to both the:\nIssuenator macOS App Issuenator website The Issuenator macOS App #Overview #Issuenator is designed with privacy in mind. Your data stays on your device.\nData Collection #Issuenator does not collect any personal data.\nNo analytics or tracking No data sent to third-party services No accounts or registration required Data Storage #All application data is stored locally on your Mac:\nIssue data: Stored in a local SwiftData database GitHub API token: Stored securely in the macOS Keychain Settings and preferences: Stored locally in app storage GitHub API #Issuenator communicates only with GitHub\u0026rsquo;s API to fetch issue data from repositories you\u0026rsquo;ve added. This requires a GitHub personal access token that you provide. The token is:\nStored securely in macOS Keychain Used only to authenticate with GitHub\u0026rsquo;s API Never sent anywhere else Log Data #If you request support for a bug, I may ask for details about your app usage or Log Data from your device to help me reproduce and diagnose the bug. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing my Service, the time and date of your use of the Service, and other statistics. Providing that information is completely up to you, and I only use that data to debug issues you report.\nIssuenator also prints data to a log that you can access while the app is running. That data is only retained in memory during app execution, and is cleared when you close the app. That information never leaves your machine. You can clear this log at any point during app execution. You can optionally export the log to a local file to copy details for debugging, but that requires you to manually export the data.\nThird-Party Services #Issuenator does not integrate with any third-party analytics, advertising, or data collection services.\nData Deletion #To remove all Issuenator data:\nDelete the app from your Mac Remove the API token from Keychain Access (search for \u0026ldquo;Issuenator\u0026rdquo;) Issuenator Website #Information Collection and Use #The Issuenator website does not directly collect any personal information. However, if you submit a request through the website form, I request personally identifiable information including Name, Email address, and information about your request. I only collect this information for the replying to your query. I never share this information with any other party. I will retain the information for a period of up to one year. At that time, I will delete any personally identifable information. You may contact me at any time through the form at the Website to request deletion of your personal information.\nCookies #Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. These are sent to your browser from the websites that you visit and are stored on your device\u0026rsquo;s internal memory.\nThe Issuenator Website does not use these “cookies” explicitly. However, the Website may use third-party code and libraries that use “cookies” to collect information and improve their services. A full list of these third-party services is provided so you may examine their Privacy Policies.\nService Providers #I may employ third-party companies and individuals due to the following reasons:\nTo facilitate our Website; To provide the Website on our behalf; To perform Website-related services; or To assist us in analyzing how our Website is used. I want to inform users of this Website that these third parties may have access to personal data. Third-party services may use analytics to collect usage about their product. However, they are obligated not to disclose or use the information for any other purpose.\nCurrently, the third-party companies and services used on this Website are:\nFormspree Hugo Dreamhost Security #I value your trust in using my Website and app, thus I strive to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and I cannot guarantee its absolute security.\nLinks to Other Sites #This Website may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by me. Therefore, I strongly advise you to review the Privacy Policy of these websites. I have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.\nChildren’s Privacy\nI do not knowingly collect personally identifiable information from children. I encourage all children to never submit any personally identifiable information through the Application and/or Website. I encourage parents and legal guardians to monitor their children\u0026rsquo;s Internet usage and to help enforce this Policy by instructing their children never to provide personally identifiable information through the Application and/or Website without their permission. If you have reason to believe that a child has provided personally identifiable information to me through the Application and/or Website, please contact me. You must also be at least 16 years of age to consent to the processing of your personally identifiable information in your country (in some countries we may allow your parent or guardian to do so on your behalf).\nContact #If you have questions about this privacy policy, please contact the developer via GitHub Issues.\n","date":null,"permalink":"/privacy/","section":"Issuenator","summary":"Privacy Policy #Last updated: January 2026\nOverview #Issuenator is a macOS app written by Dachary Carey.\nThe Issuenator website is designed to provide information about the Issuenator app for users who may be interested in its functionality.","title":"Privacy Policy"},{"content":"Get Help #Having trouble with Issuenator? Here\u0026rsquo;s how to get support.\nGitHub Issues #The best way to report bugs or request features is through GitHub Issues:\nReport a Bug Request a Feature Common Questions #How do I get a GitHub API token?\nIssuenator requires a GitHub personal access token to fetch your issues. You can create one at github.com/settings/tokens. See the API Key documentation for required permissions.\nWhy don\u0026rsquo;t I see issues from a private repository?\nMake sure your GitHub token has access to the repository. For fine-grained tokens, you need to explicitly grant access to each private repository.\nHow often does Issuenator fetch new issues?\nBy default, Issuenator fetches issues hourly. You can adjust this in Settings to fetch several times per hour, several times per day, or daily—either globally or per-repository.\nWhere is my data stored?\nAll data is stored locally on your Mac using SwiftData. Your GitHub token is stored securely in the macOS Keychain. Nothing is sent to any server other than GitHub\u0026rsquo;s API.\nContact #For other inquiries, you can reach the developer:\nMastodon: @dacharyc Website: dacharycarey.com Or send a message using the form below:\nYour Name Email Address Message Send Message ","date":null,"permalink":"/support/","section":"Issuenator","summary":"Get Help #Having trouble with Issuenator? Here\u0026rsquo;s how to get support.\nGitHub Issues #The best way to report bugs or request features is through GitHub Issues:\nReport a Bug Request a Feature Common Questions #How do I get a GitHub API token?","title":"Support"},{"content":"","date":null,"permalink":"/tags/","section":"Tags","summary":"","title":"Tags"}]