From 6d9d1bcd82e1aeb80286e0e197f4a2dba2d1bbce Mon Sep 17 00:00:00 2001 From: Erik Simon Date: Tue, 28 Jul 2026 21:27:32 +0200 Subject: [PATCH] Require feature/fix branches instead of direct master commits Co-Authored-By: Claude Sonnet 5 --- CLAUDE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index beec172..eb64572 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -6,6 +6,10 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co `hypr-chrome` is a Hyprland compositor plugin (a `.so` loaded via `hyprctl plugin load`). It draws a chamfered HUD-style border frame behind every window, expanded past the window's own edges, plus a floating title bar hanging off the top-left corner. It is a C++ shared library built against Hyprland's plugin API/headers — there is no application logic outside the compositor plugin lifecycle. +## Workflow + +Do not commit directly to `master`. All feature work goes on a `feature/` branch and all bug fixes go on a `fix/` branch, merged back via PR. + ## Build Requires the Hyprland headers/libs (`hyprland`, `libdrm`, `libinput`, `libudev`, `wayland-server`, `xkbcommon`, `pixman-1`, cairo, etc., all ABI-matched to a specific Hyprland build). A pinned Nix flake dev shell provides all of it: