alunduil / alunduil/zfs-replicate

Default branch is main across GitHub, CI, and dependency bots

未關閉
#400 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
enhancement
主要語言
Python
星號
24
分支
6
平均合併
3 小時 11 分鐘
30 天內合併 PR
49

描述

## User story

As a **contributor**, I want **`main` to be the default branch across GitHub, CI, and dependency bots** so that **my PRs target the same branch everyone else does and CI fires on the same ref**.

## Why

The GitHub default is `master`, but `.github/workflows/pre-commit.yml` triggers on `branches: [main]`. That means pushes to `master` do not run the pre-commit workflow — a silent gap. Renovate's PR #389 also proposes targeting `develop`, `main`, and `master` simultaneously. A single canonical branch removes drift.

## Acceptance criteria

- [ ] Default branch on GitHub is renamed `master` → `main`.
- [ ] Every workflow in `.github/workflows/*.yml` that references `main` or `master` uses `main` only.
- [ ] `renovate.json` (when #389 is merged) has `baseBranchPatterns: ["main"]`.
- [ ] README, CONTRIBUTING, and any docs that link to `…/blob/master/…` are updated to `…/blob/main/…`.
- [ ] Open PRs have their base branch retargeted to `main`.
- [ ] Branch protection rules moved from `master` to `main`.

## Out of scope

- Deleting the old `master` ref (GitHub keeps a redirect; leaving it is safer for external forks).

## Notes

- Target release: **none — chore**
- Hard prerequisite for the release-please and Renovate chores.
- Source: modernization assessment §1, §4.

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。