Repository navigation
Option to set default branch at repository creation - #10803
Merged
Merged
Conversation
Fix go-gitea#9542 Signed-off-by: Andrew Thornton <art27@cantab.net>
zeripath
added
the
type/feature
Signed-off-by: Andrew Thornton <art27@cantab.net>
Codecov Report
@@ Coverage Diff @@
## master #10803 +/- ##
=======================================
Coverage 43.53% 43.53%
=======================================
Files 589 589
Lines 82683 82698 +15
=======================================
+ Hits 35993 36004 +11
+ Misses 42221 42212 -9
- Partials 4469 4482 +13
Continue to review full report at Codecov.
|
GiteaBot
added
the
lgtm/need 2
Member
|
Could this be added to the |
Contributor
Author
|
@mrsdizzie Done - Sorry I missed it. |
mrsdizzie
approved these changes
Mar 25, 2020
GiteaBot
added
lgtm/need 1
guillep2k
approved these changes
Mar 26, 2020
guillep2k
left a comment
guillep2k
left a comment
Member
There was a problem hiding this comment.
Requires make generate-swagger. Otherwise looks good to me.
GiteaBot
added
lgtm/done
Contributor
Author
|
d'oh |
zeripath
pushed a commit
that referenced
this pull request
Jul 5, 2020
…er default branch (#12135) This fixes an issue I noticed with #10803: when you create a repo with a non-master default branch, gitea doesn't change the remote ref HEAD, so it still points at refs/heads/master. As a result, cloning my repos gives me error messages and doesn't check out the desired default branch, so I need to manually check it out after cloning.
techknowlogick
pushed a commit
to techknowlogick/gitea
that referenced
this pull request
Jul 8, 2020
…er default branch (go-gitea#12135) This fixes an issue I noticed with go-gitea#10803: when you create a repo with a non-master default branch, gitea doesn't change the remote ref HEAD, so it still points at refs/heads/master. As a result, cloning my repos gives me error messages and doesn't check out the desired default branch, so I need to manually check it out after cloning.
techknowlogick
added a commit
that referenced
this pull request
Jul 8, 2020
…er default branch (#12135) (#12182) This fixes an issue I noticed with #10803: when you create a repo with a non-master default branch, gitea doesn't change the remote ref HEAD, so it still points at refs/heads/master. As a result, cloning my repos gives me error messages and doesn't check out the desired default branch, so I need to manually check it out after cloning. Co-authored-by: xenofem <45297511+xenofem@users.noreply.github.com>
ydelafollye
pushed a commit
to ydelafollye/gitea
that referenced
this pull request
Jul 31, 2020
…er default branch (go-gitea#12135) This fixes an issue I noticed with go-gitea#10803: when you create a repo with a non-master default branch, gitea doesn't change the remote ref HEAD, so it still points at refs/heads/master. As a result, cloning my repos gives me error messages and doesn't check out the desired default branch, so I need to manually check it out after cloning.
abayer
pushed a commit
to abayer/gitea-go-sdk
that referenced
this pull request
Sep 3, 2020
updates from go-gitea/gitea#10803 Co-authored-by: 6543 <6543@obermui.de> Reviewed-on: https://gitea.com/gitea/go-sdk/pulls/300 Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> Reviewed-by: mrsdizzie <info@mrsdizzie.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix #9542
Also fixes bug whereby template repos without a master branch cannot be templated and master branch rather than the default branch will be templated.
Signed-off-by: Andrew Thornton art27@cantab.net
Screenshots
Repository Creation Screen
Leaving the new option blank will default to master
Empty Repository Screen
Here the new empty repository has been created with the default branch called NotMaster. Note how the instructions have changed to suggest that the initial push is sent to NotMaster rather than master.
Default Commit
A new repository created with the default branch called rabbit
From a template
A new repository called testemplate was created similar to the above - it was then marked as a template and the repository testcreate was created from it.
Example of a bad default branch name