mergiraf/mergiraf
mergiraf/mergiraf
9
213
Fork 45
Code Issues 50 Pull requests 6 Releases 19 Activity Actions

fix(postprocess/merge_same_sigs): use the revisions that the node is actually known to be in #533

Merged
ada4a merged 2 commits from ada4a/mergiraf:521 into main 2025-07-26 14:56:51 +02:00
Conversation 0 Commits 2 Files changed 5 +27 -6
ada4a commented 2025-07-25 19:30:01 +02:00
Owner
Copy link

fixes #521

fixes #521
fix
All checks were successful
/ test (pull_request) Successful in 41s
Details
ddc5675ced
wetneb approved these changes 2025-07-26 11:10:36 +02:00
wetneb left a comment
Owner
Copy link

Thanks a lot for tackling this! The fix looks very natural and correct. I'm curious about running the benchmarks on it, but I don't think it should be a blocker for merging (as in, running the benchmarks on it will mostly be testing the usefulness of the benchmarks, not your change ^^)

Thanks a lot for tackling this! The fix looks very natural and correct. I'm curious about running the benchmarks on it, but I don't think it should be a blocker for merging (as in, running the benchmarks on it will mostly be testing the usefulness of the benchmarks, not your change ^^)
❤️ 1
ada4a merged commit a3aa5f8ce9 into main 2025-07-26 14:56:51 +02:00
ada4a deleted branch 521 2025-07-26 14:56:52 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
wetneb
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind
Bad merge
Examples where the merging algorithm doesn't work as well as it should

  
Kind
Bug
Something is not working

  
Kind
Documentation
Documentation changes

  
Kind
Enhancement
Improve existing functionality

  
Kind
Feature
New functionality

  
Kind
New language

  
Kind
Security
This is security issue

  
Kind
Testing
Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Compat/Breaking
Kind
Bad merge
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
New language
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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: mergiraf/mergiraf#533
No description provided.
Delete branch "ada4a/mergiraf:521"

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?