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
{{ message }}
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
Visiting the repository shows the branch that was last pushed to in the menu on the right, but the contents of the master branch. Since these don't match up it makes for some confusion when checking if a push was successful.
Edit: This happens when going to the repository root (for example by clicking on Commits in the menu on the left)
The text was updated successfully, but these errors were encountered:
We either change master to refs/heads/master in ProjectResource.java#L92 so that its not incorrectly matched to any other branch matching **master in JGitRepositoryFacade.java#L157, or we should replace the endsWith(String) with an equals(String) comparison. The cleanest solution seems to be to prepend refs/heads/ if its not given, and then use an equals comparison instead. I think that's what Git is supposed to do under the hood too. But I am not certain what the side effects would be, as I remember that the branch prefix differs for bare and non-bare repositories. The git-server mostly uses bare-repositories, but not always. @LiamClark What do you think?
See also the commit devhub-tud/git-server@ac08538 which kind of proves the point we have been struggling with a related issue before (as it was included in a hotfix release).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Visiting the repository shows the branch that was last pushed to in the menu on the right, but the contents of the
master
branch. Since these don't match up it makes for some confusion when checking if a push was successful.Edit: This happens when going to the repository root (for example by clicking on Commits in the menu on the left)
The text was updated successfully, but these errors were encountered: