sixfold-space/madtea
sixfold-space/madtea
SHA256
2
0
Fork 0
Code Issues 33 Pull requests Projects Releases 11 Packages Wiki Activity Actions

ci: checkout must init with the sha256 object format #136

Merged
hexajon merged 1 commit from refs/pull/136/head into main 2026-07-15 23:48:16 +00:00
Conversation 0 Commits 1 Files changed 2 +48 -16
hexajon commented 2026-07-15 23:48:13 +00:00 (Migrated from codeberg.org)
Copy link

Summary

The first live run of the de-node'd workflows failed at every checkout with "fatal: mismatched algorithms: client sha1; server sha256": this repository uses the sha256 object format, and the new in-container checkout's bare git init created a sha1 client. Every checkout step in ci.yml and drift.yml now runs git init --object-format=sha256 with a comment explaining why. Verified end-to-end inside the runner VM with forgejo-runner exec against codeberg.org: checkout lands the exact ref and the vet job runs green. Refs #47.

## Summary The first live run of the de-node'd workflows failed at every checkout with "fatal: mismatched algorithms: client sha1; server sha256": this repository uses the sha256 object format, and the new in-container checkout's bare git init created a sha1 client. Every checkout step in ci.yml and drift.yml now runs git init --object-format=sha256 with a comment explaining why. Verified end-to-end inside the runner VM with forgejo-runner exec against codeberg.org: checkout lands the exact ref and the vet job runs green. Refs #47.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
breaking
Breaking change - flag for release notes

  
bug
Something is not working

  
documentation
Documentation only

  
enhancement
New feature

  
epic
Tracking epic with dependency children

  
good first issue
Interested in contributing? Get started here.

  
help wanted
Maintainer would welcome outside help

  
refactoring
Code restructuring without behavior changes

  
resolution/duplicate
Closed as duplicate of another issue

  
resolution/invalid
Closed as invalid or not reproducible

  
resolution/wontfix
Closed as won't fix

  
security
Security issue or hardening

  
severity/critical
Security severity: critical

  
severity/high
Security severity: high

  
severity/low
Security severity: low

  
severity/medium
Security severity: medium

  
status/abandoned
Someone started, then walked away - up for grabs

  
status/blocked
Blocked by another issue or an external dependency

  
status/needs-decision
Waiting on a maintainer decision; workable once decided

  
status/needs-info
Waiting on reporter / more information before work can start

  
status/needs-verification
Done except verification in a live interactive session

  
testing
Test suite / CI infrastructure work

  
upstream
Related to an upstream repository, already reported there

No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!136
No description provided.