<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Contributing :: Go Kure</title><link>https://www.gokure.dev/kure/dev/contributing/index.html</link><description>Contributing Resources for contributing to Kure.
Development Guide - Setup, testing, code quality, and CI/CD workflows GitHub Workflows - CI/CD pipeline documentation Quick Start # Clone the repository git clone https://github.com/go-kure/kure.git cd kure # Install tools make tools # Run checks make check # Run full pre-commit validation make precommit Branch Workflow main is protected. Create a feature branch:
git checkout -b feat/my-feature main # make changes git push -u origin feat/my-feature gh pr create Required CI checks: lint, test, build.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.gokure.dev/kure/dev/contributing/index.xml" rel="self" type="application/rss+xml"/><item><title>Development Guide</title><link>https://www.gokure.dev/kure/dev/contributing/guide/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.gokure.dev/kure/dev/contributing/guide/index.html</guid><description>Development Guide This guide covers development workflows and tooling for the Kure project.
Quick Start # Get help with all available commands make help # Run all standard development tasks make all # Quick development cycle make check Contributing Workflow The main branch is protected — all changes must go through pull requests.
Branch Workflow Create a feature branch from main:
git checkout -b feat/my-feature main Use branch prefixes: feat/, fix/, docs/, chore/</description></item><item><title>GitHub Workflows</title><link>https://www.gokure.dev/kure/dev/contributing/github-workflows/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.gokure.dev/kure/dev/contributing/github-workflows/index.html</guid><description>GitHub Workflows Documentation This document provides an overview of all GitHub Actions workflows used in the kure project.
Last Updated: 2026-02-27
Workflow Summary Workflow File Triggers Purpose CI ci.yml push, PR, schedule, manual Comprehensive testing, linting, building, security Deploy Docs deploy-docs.yml push to main (docs paths), workflow_dispatch Multi-version docs deployment Manage Docs manage-docs.yml workflow_dispatch Remove, rebuild, or re-point doc versions Auto-Rebase auto-rebase.yml push to main Rebase all open PRs when main is updated Release release.yml version tags GoReleaser-based release with versioned docs deploy Create Release release-create.yml workflow_dispatch Pre-release test gate + tag creation PR Review pr-review.yml pull_request Two-pass AI code review via ccproxy CI Workflow File: .github/workflows/ci.yml Name: CI</description></item><item><title>Dependency Updates</title><link>https://www.gokure.dev/kure/dev/contributing/dependency-updates/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.gokure.dev/kure/dev/contributing/dependency-updates/index.html</guid><description>Dependency Updates Guide This guide covers the process for updating Kure’s dependencies, including version tracking, risk assessment, and coordinated upgrades.
Version Management Overview Kure tracks dependency versions in three places:
File Purpose go.mod Go module dependencies (authoritative for build) versions.yaml Version metadata: current version, supported range, constraints docs/compatibility.md Generated from versions.yaml — never edit directly The sync-versions.sh script validates consistency between go.mod and versions.yaml, and regenerates docs/compatibility.md.
Update Risk Levels Patch Updates (Low Risk) Patch bumps (e.g., v1.5.0 → v1.5.1) contain bug fixes only.</description></item></channel></rss>