You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tracking: open PRs frozen pending maintainer review (stacks and merge order) #324
PRs are paused at the maintainer's request: the recent wave caused merge conflicts with in-progress batching work, because new PRs reworked code that older PRs were already fixing. I will not open new PRs, and will not push or rebase existing ones, until I get the go-ahead.
This issue is an index of my open PRs so they can be triaged, ordered and batched (or closed) at the maintainer's pace. Nothing here needs action right now. Happy to close, squash or split anything on request.
Wave of 2026-10-08 to 2026-10-10 (opened after the batches)
Many of these are stacked (base is another PR branch, not main). Merge order must follow the stack.
Stack A: alignment core / STAR parity (base main at #295)
#295 stitch annotated junctions, drop covered PE sub-alignments
└ #301 never stitch same-diagonal seeds, PE junction walk
└ #302 seed-overlap order, insertions, sjdb overhang
└ #304 window formation / per-window dedup for long splices
└ #311 last yeast differences
├ #312 sjdb insertion at mapping time
└ #315 Aligned.toTranscriptome.out.bam record for record
├ #321 multimappers in STAR's window order
└ #316 outFilterType BySJout / SJ.out.tab filtering
└ #317 twopassMode Basic as STAR
└ #320 genomeSAsparseD in seed search
Dependabot: #259 (noodles 0.116, already in #289, can close), #285, #286.
Hot spots (files touched by many PRs)
src/io/sam.rs, src/align/stitch.rs, src/align/read_align.rs, src/params/mod.rs, src/lib.rs. Any PR touching these should go through a batch rather than be merged on its own.
Proposal
When the maintainer is ready, I can: close the superseded ones (#294, #259, possibly #322 or the Stack A pieces), rebase a single stack at a time onto main, and re-run the STAR parity checks before each batch. Until then, frozen.
Context
PRs are paused at the maintainer's request: the recent wave caused merge conflicts with in-progress batching work, because new PRs reworked code that older PRs were already fixing. I will not open new PRs, and will not push or rebase existing ones, until I get the go-ahead.
This issue is an index of my open PRs so they can be triaged, ordered and batched (or closed) at the maintainer's pace. Nothing here needs action right now. Happy to close, squash or split anything on request.
Already merged (maintainer batches)
#284 (chimeric multimap), #289 (Batch1), #290 (Batch2), #291 (
mappedFilter), #307 (WithinBAM, PE nM)Wave of 2026-10-08 to 2026-10-10 (opened after the batches)
Many of these are stacked (base is another PR branch, not
main). Merge order must follow the stack.Stack A: alignment core / STAR parity (base
mainat #295)Stack B: SAM optional tags (base
mainat #306)Stack C: gene model from index (base
mainat #308)Standalone on
mainalign/seed.rs)index/sa_index.rs)--outSAMtype BAM Unsorted SortedByCoordinate--readFilesInlistsUmbrella / overlapping
Older open PRs (before the batches)
mappedFilter(supersedes #169, #252); TranscriptomeSAM crash fix and--quantModevalidation from #283 #291)Dependabot: #259 (noodles 0.116, already in #289, can close), #285, #286.
Hot spots (files touched by many PRs)
src/io/sam.rs,src/align/stitch.rs,src/align/read_align.rs,src/params/mod.rs,src/lib.rs. Any PR touching these should go through a batch rather than be merged on its own.Proposal
When the maintainer is ready, I can: close the superseded ones (#294, #259, possibly #322 or the Stack A pieces), rebase a single stack at a time onto
main, and re-run the STAR parity checks before each batch. Until then, frozen.