Skip to content

Conversation

mmdoogie
Copy link
Contributor

Fixes #18413 and updates associated test

Respectfully, PR #18422 does not work as submitted, as GetDefaultBranch returns the full ref string which would have to be trimmed down to get just the branch name. Why perform another git command call and several string manipulations, for a value that's ultimately not used in any meaningful way?

@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jan 27, 2022
@delvh
Copy link
Member

delvh commented Jan 27, 2022

This PR conflicts directly with #18422.
We have to decide now which of the two approaches is better, and for me, it's #18422.

@mmdoogie
Copy link
Contributor Author

Cancelling this PR, I like the updated approach in the other one now.

@mmdoogie mmdoogie closed this Jan 27, 2022
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 1 This PR needs approval from one additional maintainer to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error when creating new repo: branch does not have any commits
4 participants