You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rolling back to the prior commit of gittea fixes the problem.
There's likely a logic error where Admin / creator accounts aren't being read in correctly (or their permissions aren't being read in correctly).
Screenshots
If this issue involves the Web Interface, please include a screenshot
The text was updated successfully, but these errors were encountered:
wyattoday
changed the title
Pull request #947 breaks HTTPS push/pull request on Admin account
Pull request #947 breaks HTTPS push/pull to "master" when logged in as Admin
May 18, 2017
The proposed fix still breaks things (or leaves things broken). For example, as an admin user, when cloning an existing repository, I get an empty directory:
git.exe clone --progress -v "https://example.com/git/repository_name.git" "C:\Users\USERNAME\Documents\repository_name"
Cloning into 'C:\Users\USERNAME\Documents\repository_name'...
warning: You appear to have cloned an empty repository.
Success (641 ms @ 5/19/2017 8:08:51 AM)
Other things are broken as well (pulling still broken, haven't tried pushing yet).
Rolling back to before fd6034a fixes things for me.
[x]
):Description
This commit break pushing and pulling on "master" branch when using HTTPS and logged in as an "admin" account: fd6034a
Here's the pull request in question: #947
Rolling back to the prior commit of gittea fixes the problem.
There's likely a logic error where Admin / creator accounts aren't being read in correctly (or their permissions aren't being read in correctly).
Screenshots
If this issue involves the Web Interface, please include a screenshot
The text was updated successfully, but these errors were encountered: