github-issues

How to build interactive experiences with canvases (opens in new tab)

Canvases extend GitHub Copilot beyond text-based conversations by providing shared, interactive workspaces where developers and agents can visualize information and take action together. They are useful for tasks such as triaging issues, exploring code architecture, managing worktrees, and searching organizational knowledge. The article concludes that canvases make AI workflows more engaging, practical, and easier to iterate on. ## How canvases work - Canvas extensions are interactive surfaces within the GitHub Copilot app. - Agents can update the canvas while users interact through clicks, edits, swipes, and other controls. - User actions may be sent back to the agent or handled locally. - Developers create one by running `/create-canvas` in a Copilot agent session and describing the desired interface and capabilities. - Canvases can evolve through follow-up prompts that add features or refine existing behavior. ## Visual issue triage - A card-based interface displays GitHub Issues one at a time. - Users swipe right to ship an issue or left to reject it. - The canvas updates immediately, organizing issues into decision-based categories. - This replaces a slower, text-heavy review process with direct visual interaction. ## Interactive codebase diagrams - A generated diagram represents components of a project as connected nodes. - Users can hover over, drag, and filter elements to explore relationships and architectural layers. - The interface turns static codebase documentation into an explorable model. ## Managing sessions and worktrees - A canvas can display active GitHub Copilot sessions and their associated Git worktrees. - It distinguishes active, stale, and orphaned worktrees. - Cleanup actions are available directly from the interface, reducing manual maintenance. ## Improving agent prompts - The prompt coach reviews previous agent interactions. - It identifies issues such as unclear context, spelling mistakes, and syntax problems. - It suggests ways to make prompts more precise and improve future agent results. ## Finding organizational knowledge - A knowledge finder can search sources such as Slack, Teams, email, and documentation. - It identifies people connected to a file or topic. - Results explain both who has relevant context and where that connection was found, making it easier to locate the right expert. ## Getting started Canvases are best suited to workflows where visual understanding and direct manipulation are more effective than sequential prompts. Developers can try them in the GitHub Copilot app by using `/create-canvas`, then iterating with the agent to build a workspace tailored to their task.

From latency to instant: Modernizing GitHub Issues navigation performance (opens in new tab)

Alexander is a senior software engineer on GitHub’s Issues team, where he focuses on making developer workflows feel fast and seamless. His background spans computer graphics, machine learning, and geospatial software, giving him a broad technical perspective. ### Professional Role - Works on the GitHub Issues team. - Focuses on improving everyday developer workflows. - Enjoys finding creative ways to make interactions feel instant. ### Technical Background - Computer graphics - Machine learning - Geospatial software The provided content is a short professional biography rather than a technical blog post, so it does not include a specific argument, technical explanation, or conclusion.

GitHub for Beginners: Getting started with GitHub Issues and Projects (opens in new tab)

GitHub Issues and Projects work together to organize tasks, bugs, ideas, and broader project goals. Issues capture individual pieces of work, while Projects provide visual planning and tracking through boards, views, workflows, and charts. The post introduces beginners to creating an issue, building a Kanban project, and managing progress collaboratively. ## Why Issues and Projects Matter - Issues provide a shared space for tracking bugs, tasks, and ideas. - Projects organize issues into a larger workflow for planning and prioritization. - Using both tools helps teams coordinate work, communicate progress, and avoid missed tasks. ## Creating a GitHub Issue - Open a repository and select the **Issues** tab, then click **New issue**. - Add: - A clear title. - A detailed description explaining the expected behavior or required change. - An assignee. - Labels for classification. - An issue type, such as a bug or task. - A related project or milestone. - After creation, team members can comment and collaborate. - Typing `#` followed by an issue number creates a clickable link to another issue. - Completed work can be marked by closing the issue. ## Creating a GitHub Project - Open the repository’s **Projects** tab and click **New project**. - Choose the **Kanban** template, name the project, disable bulk import, and create it. - GitHub automatically provides columns, which can be customized. - Multiple project tabs offer different ways to view and manage the same work. ## Managing and Customizing Projects Project settings allow users to: - Control access permissions. - Create or modify custom fields. - Rename the project and edit its description. - Add a README. - Copy the project board. - Change project visibility. ### Insights and Charts - The **Insights** section provides charts for analyzing project data. - Charts can be customized through the **Configure** menu, including their layout and displayed information. ### Automated Workflows - Built-in workflows can update item statuses automatically. - Examples include: - Setting new items to `todo`. - Closing issues when their project status changes. - Marking items as `Done` when an issue is closed. ### Project Status Updates - The **Add status update** feature lets teams report project health and progress directly from the project view. GitHub beginners can start with well-written issues and then connect them to a Kanban Project board. Custom fields, automated workflows, charts, and status updates make it easier to turn individual tasks into a transparent, trackable team workflow.