all_git_branches() returns empty owner_name for personal branches
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start at the generated Python SDK entry points for all_git_branches() and git_branch(), comparing how each represents personal branches and owner_name. Reproduce the issue with the provided calls, then verify that all_git_branches() returns the owner's full name for personal branches without requiring a separate branch switch.
Written by the indexing model from the issue text.
Description
Summary
sdk.all_git_branches(project_id) returns owner_name: "" (empty string) for personal branches where personal: True, while sdk.git_branch(project_id) correctly returns the owner's full name for the same branch.
Expected behavior
all_git_branches() should populate owner_name for personal branches, matching the behavior of git_branch().
Reproduction
SDK: looker-sdk v26.4.0 (Python)
Looker: Google Cloud core 26.2
Python: 3.13.3
import looker_sdk
sdk = looker_sdk.init40()
# Enable dev mode
sdk.update_session(looker_sdk.models40.WriteApiSession(workspace_id="dev"))
# List all branches — owner_name is empty for personal branches
branches = sdk.all_git_branches("my_project")
for b in branches:
if b.personal:
print(f"all_git_branches: name={b.name}, personal={b.personal}, owner_name={b.owner_name!r}")
# Output: all_git_branches: name=dev-user-xxxx, personal=True, owner_name=''
# Get current branch — owner_name is populated
current = sdk.git_branch("my_project")
print(f"git_branch: name={current.name}, personal={current.personal}, owner_name={current.owner_name!r}")
# Output: git_branch: name=dev-user-xxxx, personal=True, owner_name='FULL NAME'
Actual results
| Method | personal |
owner_name |
|---|---|---|
sdk.all_git_branches() |
True |
'' (empty) |
sdk.git_branch() |
True |
'FULL NAME' |
Impact
Consumers of all_git_branches() cannot identify who owns each personal branch without making an additional git_branch() call per branch (by switching to each one). This affects tools that display branch listings with ownership information.
Environment
- SDK:
looker-sdk26.4.0 (Python, pip) - API version: 4.0
- Looker instance: Google Cloud core 26.2
- OS: macOS (darwin/arm64)
- Dominant language
- TypeScript
- Stars
- 272
- Forks
- 203
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from looker-open-source/sdk-codegen
-
need triage p3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
looker-open-source/sdk-codegen#1741 ·
-
need triage p3
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
looker-open-source/sdk-codegen#1714 ·
-
need triage p3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
looker-open-source/sdk-codegen#1705 ·
-
bug p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
looker-open-source/sdk-codegen#1677 ·
-
p3
Difficulty 1/5 Under an hour Newbie friendliness 68/100
looker-open-source/sdk-codegen#487 · 2 comments ·
All issues in looker-open-source/sdk-codegen
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·