Skip to content

fix(ci): unblock auto-release pipeline + cut v1.0.0 next merge #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xergioalex merged 2 commits into from
May 2, 2026
Merged

fix(ci): unblock auto-release pipeline + cut v1.0.0 next merge #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
98943ec
docs(readme): mention v1.0.0 in version examples and add bug-report tip
xergioalex May 2, 2026
8e64843
docs(agents): forbid direct push to main in Common Mistakes (#22)
xergioalex May 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -315,6 +315,7 @@ See [docs/DEVELOPMENT_COMMANDS.md](docs/DEVELOPMENT_COMMANDS.md) for full refere
19. Add a Click flag without a short alias if the existing command in the same group already uses one (consistency)
20. Forget the `\b` marker in Click docstrings — without it, Click reflows your example block
21. Drop scratch files anywhere outside `tmp/` (draft PR bodies, debug dumps, sample payloads, etc.) — see Rule 17
22. **Push directly to `main`** — even a one-line workflow fix or a `pyproject.toml` toggle MUST go through a feature branch + PR + the `code_check.yml` gate. The only exception is the `chore(release): X.Y.Z [skip ci]` commit that `auto-release.yml` itself makes automatically. Force-pushes to `main` are forbidden without explicit, scoped permission for that exact operation.

### DO

Expand Down
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The CLI exposes two ways to inspect what's installed — a quick one-liner for s
```bash
# Single-line, scriptable
dailybot --version
# → dailybot 0.5.0 (Python 3.12.4)
# → dailybot 1.0.0 (Python 3.12.4)

# Multi-line panel: version, Python runtime, install path, release notes link
dailybot version
Expand All @@ -42,7 +42,9 @@ dailybot version
dailybot version --check
```

`dailybot version --check` is the recommended way to find out whether you should upgrade. If a newer release is available, the output also lists the upgrade command for each install method (Homebrew, Linux binary, pipx, pip).
`dailybot version --check` is the recommended way to find out whether you should upgrade. If a newer release is available, the output lists the upgrade command for each install method (Homebrew, Linux binary, pipx, pip), so you don't need to remember which channel you used to install in the first place.

> **Bug reports?** Always include the full output of `dailybot version` — the install path and Python runtime are usually enough to tell us whether the issue is in the CLI itself, in a transitive dep, or in the host environment.

## For humans

Expand Down
Loading