cli/git
Tyler McGoffin 4575692ebf Remove private readBranchConfig method and remove parseBranchConfig from Client
I think I went too far with my previous refactor and am backing out of it.
Adding a private readBranchConfig method on the client wasn't providing
any real additional value, so I've put it back into ReadBranchConfig.

However, I think there is still value in having parseBranchConfig
(formerly createBranchConfig) as a separate util function, as it both
improves readability of ReadBranchConfig and makes parsing its purpose
easier through the bespoke tests for it.
2025-01-08 10:36:45 -08:00
..
fixtures Refactor code to live inside default pkg 2022-05-18 08:40:30 +02:00
client.go Remove private readBranchConfig method and remove parseBranchConfig from Client 2025-01-08 10:36:45 -08:00
client_test.go Remove private readBranchConfig method and remove parseBranchConfig from Client 2025-01-08 10:36:45 -08:00
command.go Allow client push to use insecure credential pattern 2024-11-26 22:29:58 +01:00
errors.go Refactor git client and add tests (#6525) 2022-11-03 11:58:38 +01:00
objects.go Move trackingRef into pr create package 2025-01-06 10:33:28 -06:00
url.go Merge pull request #8929 from cli/wm/parse-url-no-nakaed-return 2024-04-05 16:33:09 +02:00
url_test.go Merge pull request #8929 from cli/wm/parse-url-no-nakaed-return 2024-04-05 16:33:09 +02:00