Find meaningful ways to contribute

This feature aims to prevent the loss of authoring conversations when a pod restarts by capturing backend-specific resume IDs. The goal is to allow CLI commands to resume interrupted sessions using these IDs, rather than starting a new conversation. The issue outlines open design questions regarding which backends support resume IDs, staleness limits, and how to handle respawning agents.

This feature aims to route human review comments and submissions on agent-authored pull requests directly to the authoring agent. Currently, these comments are not specifically directed, leading to potential delays or missed feedback. The proposed solution involves collecting these events and delivering them to the authoring agent through existing delivery mechanisms.

The project is seeking 20 users to participate in a closed beta test of their app on Google Play for at least 14 days. Testers need to join a Google Group, opt-in as a tester, and install the new version alongside the existing app without needing to uninstall it.

This issue is a beginner-friendly task to add a new Japanese proverb to a JSON file. No coding is required, and the contribution can be made directly from the browser in under a minute. The task involves forking the repository, editing a specific JSON file to include the proverb's Japanese, Romaji, English translation, and meaning, and then submitting a pull request.

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

The pre-merge coverage gate is failing to detect new, untested subpackages within `pkg/hub/*`. Specifically, the `pkg/hub/wire` package is dead, untested, and invisible to CI due to filtering in the `v2-tests.yml` workflow, allowing it to pass coverage checks incorrectly. The issue recommends deleting the dead package to fix this.

This issue addresses two minor cleanup tasks in the kornia-3d crate. First, it proposes renaming and removing temporary comments from a useful regression test to make it more permanent. Second, it suggests removing a reference to an external codebase ('lightweight_vio') from public rustdoc comments to improve clarity for users.

This issue proposes adding support for various bit depths beyond the current 8-bit limitation in the Bitmap class. The goal is to enable the handling of BMP images with different pixel formats as defined by the BMP file specification.

This issue proposes adding a feature to disable the 'thinking' or reasoning process for chat answers in the SurfSense application. Currently, this process consumes tokens and can delay or shorten responses, especially with smaller local models. The necessary mechanism already exists and is used for title generation, and this issue outlines the specific code locations for implementation.

This bug report details two performance issues in Omnigent's native forwarders. Firstly, they repeatedly re-read entire vendor files instead of just new data, and secondly, they endlessly retry unresolvable items. These inefficiencies, particularly with Claude sub-agents, can lead to excessive CPU usage.

This issue proposes a security enhancement for the Copilot feature by moving the storage of the Copilot user OAuth token from agent-readable files/environment variables to the hub. The token will then be injected server-side into `/copilot_internal/` requests, similar to how GitHub App tokens are handled, improving security for agents that have proxy injection enabled.

Self-hosted CI runners in the hivecommons/hive environment are failing to set up jobs due to a "No space left on device" error. This is occurring during the download of the `actions/checkout` action, preventing any code from running. The issue appears to be a shared resource problem on the runner scale set, requiring disk space to be freed or the runners to be recycled.

This issue proposes evaluating the official `docker/go-sdk` as a replacement for the current `github.com/docker/docker/client` integration. The goal is to improve context-aware container runtime support, specifically addressing how the CLI resolves Docker contexts and their associated socket paths. The evaluation will involve testing various capabilities and compatibility scenarios to determine if the SDK can be adopted.

This issue reports broken external links detected by an automated test. Several links, specifically to `shop.empire-electronic.de`, are returning 404 Not Found errors across multiple test runs. This indicates a problem with the external website or the links pointing to it.

Seven platform builds are currently unassigned, meaning no single person is responsible for testing and maintaining them. This has led to bugs that go unnoticed until users discover them, as the automated CI checks only verify compilation and basic structure, not actual platform behavior. The issue seeks owners for each platform to ensure their proper functioning.

This feature request aims to create a set of reusable, modern styles for modal forms to ensure visual consistency across the platform. The current 'report problems' modal is outdated, and the proposed solution involves developing general styles that can be applied to other similar forms, improving maintainability and aesthetics.

This issue requests the creation of a tool, either a Claude Code skill or a bash script, to automatically generate a structured CHANGELOG.md file from git history. The tool should fetch commits since the last tag, categorize them into 'Added', 'Fixed', 'Changed', and 'Removed', and produce a well-formatted changelog. It needs to be tested on a real repository with sample output provided.

This issue proposes improvements to the CI system to better handle runner infrastructure failures. It suggests classifying failures into 'infra' or 'code', automatically rerunning infrastructure failures once, and alerting when the infrastructure failure rate exceeds a threshold. The goal is to prevent misleading reports and improve debugging efficiency.