Skip to content

[AIR-3028] qs: fix buildDevBranchName: the functionality is duplicated#133

Merged
host6 merged 1 commit intountillpro:mainfrom
host6:AIR-3028-qs-fix-buildDevBranchName-the-functionality-is-dup-pr
Feb 23, 2026
Merged

[AIR-3028] qs: fix buildDevBranchName: the functionality is duplicated#133
host6 merged 1 commit intountillpro:mainfrom
host6:AIR-3028-qs-fix-buildDevBranchName-the-functionality-is-dup-pr

Conversation

@host6
Copy link
Collaborator

@host6 host6 commented Feb 23, 2026

AIR-3028 qs: fix buildDevBranchName: the functionality is duplicated
https://untill.atlassian.net/browse/AIR-3028

@augmentcode
Copy link

augmentcode bot commented Feb 23, 2026

🤖 Augment PR Summary

Summary: This PR refactors the qs dev branch-creation flow to remove duplicated functionality and make branch-existence validation consistent.

Changes:

  • Simplified gitcmds.CreateDevBranch by removing the internal “remote branch exists” check and its extra parameter.
  • Refactored the GitHub-issue workflow: branch name generation is moved into BuildDevBranchName (now returns both branch name and notes derived from the issue title).
  • Renamed CreateGithubLinkToIssue to LinkBranchToGithubIssue and reordered the flow so the git branch is created/pushed before attempting GitHub issue linkage.
  • Centralized local+remote branch existence checks into internal/commands/dev.go for all workflows (GitHub/Jira/custom).
  • Replaced the go-git based branch existence check with direct git CLI calls.
  • Added uspecs documentation (change request + implementation plan) describing the rationale and expected pipeline.

Technical Notes: GitHub issue titles are fetched via gh issue view --json title, and dev-branch naming now consistently appends the -dev suffix after sanitization.

🤖 Was this summary useful? React with 👍 or 👎

@host6 host6 merged commit e2c33d2 into untillpro:main Feb 23, 2026
0 of 3 checks passed
@host6 host6 deleted the AIR-3028-qs-fix-buildDevBranchName-the-functionality-is-dup-pr branch February 23, 2026 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant