alunduil/zfs-replicate

AI Summary: The Hypothesis `SNAPSHOTS` strategy currently generates identical filesystem names, preventing tests from exercising multi-filesystem scenarios. This issue proposes modifying the strategy to produce genuinely distinct names, ensuring proper testing of the planner's handling of multiple filesystems. A sanity test will be added to verify name variation, and existing tests must remain functional.

AI Summary: This issue addresses a problem where the DevContainer build process relies on feature images from an archived GitHub organization (`devcontainers-contrib`). The goal is to update the `devcontainer.json` to use maintained feature images from `devcontainers-extra` or install the necessary tools directly via `postCreateCommand` to prevent build failures.

AI Summary: This issue proposes the creation of a `new-issue.prompt.md` file within the `.github/copilot/` directory. This prompt will guide users, especially those using AI tools like GitHub Copilot, to structure new issues consistently with an outcome-oriented title, user story, acceptance criteria, and out-of-scope sections, mirroring existing issue formats.

AI Summary: This issue proposes creating a single documentation file for commit message conventions, specifically adhering to the Conventional Commits standard. The goal is to provide clear instructions for contributors and coding agents to ensure commit messages meet repository-specific rules, which will help pass CI checks and correctly populate the CHANGELOG.

AI Summary: This issue proposes to update the `.github/copilot-instructions.md` file to redirect to `AGENTS.md`. The goal is to consolidate project-level guidance for GitHub Copilot within a single file, ensuring consistency in code conventions across human and agent-generated code. The change involves creating the redirect file with specific content and potentially appending Copilot-specific guidance.

AI Summary: This issue proposes a change to how Claude Code handles repository conventions. Instead of directly loading `CLAUDE.md`, it should redirect to `AGENTS.md` to maintain a single source of truth. The `CLAUDE.md` file will contain a redirect to `AGENTS.md` and any Claude-Code-specific guidance not relevant to `AGENTS.md`.

AI Summary: This issue proposes to automate pull request review routing by implementing GitHub's CODEOWNERS feature. The goal is to ensure that the correct person is automatically requested for reviews, preventing PRs from being delayed due to manual tagging. This will be achieved by creating a CODEOWNERS file and enabling branch protection rules.

AI Summary: This issue requests the implementation of a documented security disclosure process for the project. It aims to provide security researchers with a clear and private channel to report vulnerabilities, preventing them from having to resort to public issue trackers for sensitive information.

AI Summary: This issue proposes adding a default pull request template to the repository. The template will prompt contributors to provide a summary, link to relevant issues, and outline a test plan, aiming to improve review efficiency and clarity by ensuring essential information is provided upfront.

AI Summary: This issue proposes improving the feature request form on GitHub to encourage users to describe the problem they are trying to solve (outcome-oriented phrasing) rather than suggesting specific implementations. This will be achieved by adding guidance and structured fields to the issue template, aiming to make feature requests easier to triage and scope.

AI Summary: This issue proposes implementing a GitHub Issue Form for bug reports to ensure reporters provide essential context like version information, commands, and observed/expected behavior. This will streamline the bug reporting process by reducing the need for follow-up questions and making bugs actionable upon initial submission. The form will also include a pre-submission checkbox to encourage searching for existing issues and automatically apply a 'bug' label.

AI Summary: This issue proposes to optimize CI by automatically canceling older, redundant runs when new commits are pushed to the same branch or pull request. This will prevent wasted CI resources on superseded code, improving efficiency. The solution involves adding a `concurrency` block with `cancel-in-progress: true` to most GitHub Actions workflows, with an exception for the publish workflow.

AI Summary: This issue aims to update GitHub Actions used in workflows to reference their current major versions. This proactive update prevents CI from running on potentially deprecated runners that could cease functioning unexpectedly. The goal is a one-time catch-up before automated tools like Renovate maintain future updates.