refactor: rename Axonel to Sentinel - #9
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2d3da0cb4c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .repo | ||
| .clone() | ||
| .unwrap_or_else(|| "axonel/axonel".to_string()); | ||
| .unwrap_or_else(|| "sentinel/sentinel".to_string()); |
There was a problem hiding this comment.
Preserve the actual GitHub owner and slug
The commit description explicitly says the repository remains axonel/axonel, but this new default sends any live POST /api/v1/github/pulls request that omits the optional repo field to sentinel/sentinel, which will receive a GitHub 404 rather than create the PR. The same incorrect remote rename also appears in the package metadata and quickstart URLs, so retain axonel/axonel until the GitHub repository settings are actually renamed.
Useful? React with 👍 / 👎.
Renames the product and user-facing CLI from Axonel to Sentinel across the repository.
Migration is intentionally split into focused commits:
4-7. web UI branding
8-9. web browser/validation tests
The GitHub organization remains
axonel, and theaxonel.devorganizational domain is intentionally preserved. The repository slug is stillaxonel/axonelbecause the connected GitHub interface does not expose the repository-settings rename operation.