Skip to content

[Bug]:Quick clarification: master vs main  #2929

@pragmaton

Description

@pragmaton

Summary

Branch strategy is unclear: GitHub default is master, but docs/release workflow point to main, so it’s hard to tell what is going on.

Affected component

docs

Severity

S3 - minor issue

Current behavior

I may be misunderstanding the branch strategy.

I’m not contributing code yet; I’m just learning the project, and I’m confused about what is already released vs what is still in development.

As of March 6, 2026:

  • GitHub default branch appears to be master
  • but docs/workflows seem to describe delivery and releases around main (and dev)

References:

Which branch is the source of truth right now (master or main)? I’m asking because both branches appear to have ongoing activity...

Expected behavior

Steps to reproduce

-

Impact

Logs / stack traces


ZeroClaw version

Rust version

Operating system

Regression?

Unknown

Pre-flight checks

  • I reproduced this on the latest main branch or latest release.
  • I redacted secrets/tokens from logs.
  • I removed personal identifiers and replaced identity-specific data with neutral placeholders.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions