Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-3342GitHub issuePublicReceived

Suggestion: Consider renaming master to main for improved alignment

Reported by Rishabh-Sarang · filed Oct 18, 2025Closed upstream on 2025-10-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Suggestion: Consider renaming master to main for improved alignmentrevision 1 · captured 2026-10-04 11:42 UTC via poll

What do you need?

Hi team,

I noticed that our default branch is still named master. While it works perfectly fine, there’s been a growing movement toward renaming it to main for, let’s say, symbolic harmony with modern conventions.

GitHub itself has encouraged this change, reportedly improving repository health, global morale, and overall enlightenment across developer ecosystems.

Benefits could include:

  • Slightly warmer repo vibes
  • 0.0001% faster clone times (unverified)
  • Alignment with the moral compass of cloud infrastructure
  • Increase diversity in our commits
  • Make our repo more socially conscious than our actual code

I understand this might be a controversial step, but sometimes true progress means renaming a branch and calling it a day.

Thanks for considering this transformational initiative.

View raw text
### What do you need?

Hi team,

I noticed that our default branch is still named master. While it works perfectly fine, there’s been a growing movement toward renaming it to main for, let’s say, symbolic harmony with modern conventions.

GitHub itself has encouraged this change, reportedly improving repository health, global morale, and overall enlightenment across developer ecosystems.

Benefits could include:

- Slightly warmer repo vibes
- 0.0001% faster clone times (unverified)
- Alignment with the moral compass of cloud infrastructure
- Increase diversity in our commits
- Make our repo more socially conscious than our actual code

I understand this might be a controversial step, but sometimes true progress means renaming a branch and calling it a day.

Thanks for considering this transformational initiative.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.