#0030 Action Record Mapping #135
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/hottea!135
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/0030-action-record-mapping"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements Action Record Mapping for Forgejo heatmap SQL generation.
Changes:
src/hottea/action.py—ActionRecorddataclass +build_action()functiontests/test_action.py— 9 tests covering op_type, user IDs, repo ID, visibility scope, timestampsMapping logic:
op_type= 2 (push)user_id= 0 (visible to all)user_id=act_user_id(actor only)act_user_idfrom Forgejo user IDcreated_unixfrom commit's author dateCloses: #0030, #0023, #0024, #0025, #0026, #0027, #0028, #0029
Audit Review — PR #135
Clean Action Record Mapping implementation. All 7 issues (#0023-#0029) addressed correctly. Good use of keyword-only
is_publicparameter, proper public/private scope logic, and correct timestamp extraction from author date.No suggestions — this PR is clean and complete.
Summary
Result: COMMENT — no issues found.
APPROVED. Clean implementation, correct scope logic, good tests. Merge when ready.