alpha
Login
or
Join now
snowytrees.dev
/
project-manager
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Integrated repository, worktree, git stacker, and project manager
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
project-manager
/
src
/
project_manager
/
stacker
/
pr
/
at
master
9 files
Jordan Isaacs
stacker: reset title/body when adopting a recycled PR
3w ago
a908ac66
__init__.py
stacker: reset title/body when adopting a recycled PR create_or_update_current_pr treated every find_open_pr hit as a PR pm already owns, refreshing only the managed stack block and preserving the existing title/body. But find_open_pr matches by head ref, and stack/* branches get recycled for new work -- a reused branch can land on a still-open PR from an unrelated prior feature, whose title/description belong to the wrong work. The result was a pushed PR titled and described for the old feature (a stale "[AUTH-5322] ..." title/body surviving onto an unrelated branch). Snapshot whether pm already had a pr_state row for the branch before find_open_pr runs. With a cache row, keep the preserve-edits behavior. Without one (a fresh head-ref-search adoption), claim the PR the way a create would: set the title to this branch's bottom-commit subject and reset the body to its first commit, then let refresh_component_pr_bodies splice in the managed stack block. Adds test_push_resets_title_body_when_adopting_recycled_pr.
3 weeks ago
config.py
style: ruff format pass over src/ and tests/ Mechanical run of `uv run ruff format src tests`. No behavior change — just line wrapping and trailing-comma normalization that the project hadn't been applying. Listed in `.git-blame-ignore-revs` (added next commit) so `git blame` skips this revision.
2 months ago
create_update.py
stacker: reset title/body when adopting a recycled PR create_or_update_current_pr treated every find_open_pr hit as a PR pm already owns, refreshing only the managed stack block and preserving the existing title/body. But find_open_pr matches by head ref, and stack/* branches get recycled for new work -- a reused branch can land on a still-open PR from an unrelated prior feature, whose title/description belong to the wrong work. The result was a pushed PR titled and described for the old feature (a stale "[AUTH-5322] ..." title/body surviving onto an unrelated branch). Snapshot whether pm already had a pr_state row for the branch before find_open_pr runs. With a cache row, keep the preserve-edits behavior. Without one (a fresh head-ref-search adoption), claim the PR the way a create would: set the title to this branch's bottom-commit subject and reset the body to its first commit, then let refresh_component_pr_bodies splice in the managed stack block. Adds test_push_resets_title_body_when_adopting_recycled_pr.
3 weeks ago
find.py
cleanup naming
2 months ago
lineage.py
style: ruff format pass over src/ and tests/ Mechanical run of `uv run ruff format src tests`. No behavior change — just line wrapping and trailing-comma normalization that the project hadn't been applying. Listed in `.git-blame-ignore-revs` (added next commit) so `git blame` skips this revision.
2 months ago
refresh.py
style: ruff format pass over src/ and tests/ Mechanical run of `uv run ruff format src tests`. No behavior change — just line wrapping and trailing-comma normalization that the project hadn't been applying. Listed in `.git-blame-ignore-revs` (added next commit) so `git blame` skips this revision.
2 months ago
resolve.py
stacker: resolve PR base through merged parents; skip orphan gitlinks - pr/resolve: when a tracked parent's PR is MERGED, treat it as transparent and recurse to resolve the child's PR base against the grandparent (sync collapses a merged parent to a no-commit branch, so the child should target whatever the parent would have). Renames find_open_pr -> find_pr and distinguishes MERGED vs non-OPEN states. - pool/worktree: skip orphan gitlinks during submodule init — a gitlink in HEAD with no .gitmodules URL can never be initialized (common after an upstream submodule removal), so continue instead of erroring. - tests: cover the merged-parent PR-base resolution.
1 month ago
stack_block.py
style: ruff format pass over src/ and tests/ Mechanical run of `uv run ruff format src tests`. No behavior change — just line wrapping and trailing-comma normalization that the project hadn't been applying. Listed in `.git-blame-ignore-revs` (added next commit) so `git blame` skips this revision.
2 months ago
template.py
style: ruff format pass over src/ and tests/ Mechanical run of `uv run ruff format src tests`. No behavior change — just line wrapping and trailing-comma normalization that the project hadn't been applying. Listed in `.git-blame-ignore-revs` (added next commit) so `git blame` skips this revision.
2 months ago