Skip to content

How we work together, and how a release goes out - #2

Merged
4bit33 merged 1 commit into
mainfrom
docs/collaboration
Oct 2, 2026
Merged

4bit33 merged 1 commit into
mainfrom
docs/collaboration

Conversation

@4bit33

@4bit33 4bit33 commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Adds CONTRIBUTING.md, RELEASING.md, .github/CODEOWNERS and a pull request template, links them from both READMEs, and adds fedora / arch labels.

@W1zago — please read CONTRIBUTING.md and the Arch steps in RELEASING.md; this is the plan we discussed: one repository, packaging side by side in packaging/, short branches and PRs here instead of a fork. Approve if it suits you, or comment.

🤖 Generated with Claude Code

CONTRIBUTING.md: one repository and one code base for every distribution,
who looks after what, short branches and pull requests into the protected
main, signed commits, what to check before a PR. RELEASING.md: the version
in four places, the signed tag, then COPR and the AUR from that tag, and
who does which step. CODEOWNERS asks the right person for a review; a PR
template carries the checklist. Both READMEs link to them, and say CI runs
on Arch too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@4bit33
4bit33 requested a review from W1zago October 2, 2026 18:16
@4bit33
4bit33 merged commit d036f9d into main Oct 2, 2026
6 checks passed
@4bit33
4bit33 deleted the docs/collaboration branch October 2, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant