-
Reproduction:
- Create a new repo locally, with only one branch that isn't
master - Add a file to it, commit
- Create a new project on onedev instance
- Add as remote, then
git push -u <remote> <branch> - Refresh project on onedev instance
- Go to
Branchesunder theCodeheading for the project
- Create a new repo locally, with only one branch that isn't
-
Thanks for the reproducing steps. I followed the same but can not get it reproduced. After pushing the commit, OneDev switched to use main as default branch and branches page works fine.
Are you able to reproduce this issue everytime?
-
I'll record a video once I'm awake.
It's happened several times to several projects, and I can reproduce it every time.
Here's what the projects look like in the project list, including the test I did just now, which looks different...

If there's any info I can send to help debug this, I'll try and find it.
-
Never mind. Found the problem. Will be fixed soon. Thanks for reporting.
-
Gotcha, thanks!
I'll be waiting for the fix :3
-
OneDev
changed state to 'Closed' 3 years ago
Previous Value Current Value Open
Closed
-
OneDev
changed state to 'Released' 3 years ago
Previous Value Current Value Closed
Released
-
State changed as build #3288 is successful
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
Not Found
|
Issue Votes (0)
I just created a project, then pushed code to it. My default branch on my machines is
main, so it of course pushed to the main branch. But the default branch ismaster, and doesn't exist in the git, so I'm assuming when it tries to render the~branchesendpoint, it dies.Error Log:
'Seen Builds' set to latest; seen it for a while, not sure what version I was on when I first spotted it.