fix(#975): use hyperhive.local email domain to pass Forgejo validation
`@hyperhive` (no dot) is rejected by Forgejo's PATCH /admin/users API with 422 Unprocessable Entity. Switch to `@hyperhive.local` across all four files that construct hive-c0re/agent git emails and Forgejo account emails, so both stay in sync and pass RFC-valid domain validation.
This commit is contained in:
parent
b83edc40c6
commit
286a7c8fd3
4 changed files with 7 additions and 7 deletions
|
|
@ -142,7 +142,7 @@ fn extract_token(output: &str) -> Option<String> {
|
|||
/// Must match the `user.email` set by `meta::render_flake` so commits
|
||||
/// by the agent link back to their Forgejo profile page.
|
||||
fn agent_email(name: &str) -> String {
|
||||
format!("{name}@hyperhive")
|
||||
format!("{name}@hyperhive.local")
|
||||
}
|
||||
|
||||
/// Thin Forgejo REST helper. Sends `method` to `url` with a JSON body
|
||||
|
|
@ -227,7 +227,7 @@ async fn change_user_password(name: &str, password: &str) -> Result<()> {
|
|||
|
||||
/// Idempotently align the Forgejo account email to `agent_email(name)`.
|
||||
/// Existing agents were created with `{name}@hive.local`; this corrects
|
||||
/// that so git commits (which use `{name}@hyperhive`) link to profiles.
|
||||
/// that so git commits (which use `{name}@hyperhive.local`) link to profiles.
|
||||
/// Best-effort: failures are warned, not propagated.
|
||||
///
|
||||
/// Uses the admin REST API (`PATCH /api/v1/admin/users/{name}`) rather
|
||||
|
|
|
|||
Loading…
Reference in a new issue