Clarification: any purpose for master branch?

[leoger]

I see that the asf-site branch is both the default branch and what the TeamCity CI job tracks. The master branch is currently far behind (but not an actual ancestor of) asf-site.

I might be the only person that this ever confuses, but is there a positive reason for master to exist or does it make sense to just delete it?

[paulk-asert]

It probably can be deleted. For now I just cleaned it up. I am not sure whether all committers are familiar with the conventions for sites. Does it seem less confusing now?

[leoger]

Thanks! That's pretty obvious now, what with there being nothing there except for the README and gitignore.

It does seem to clutter the git log --graph output and similar views. Something to consider, but it's your judgment call, of course. Since there's potentially additional action, I am not closing this issue, but you should go ahead and close it when you decide.

Thanks again.

[paulk-asert]

We may still delete the branch but I am travelling at the moment and not game to try that since I probably won't get time to fix right now if anything goes wrong. I'll leave issue open for the time being.

[paulk-asert]

Hi, you can close this. I deleted the master branch some time back but forgot to report back here. Thanks again for raising this.

[leoger]

@paulk-asert, it looks like the master branch still exists: https://github.com/apache/groovy-website/tree/master 😕

[paulk-asert]

Just adding a comment which I forgot to do earlier. Currently it seems Apache has a hook on master commits, so trying to delete gives:
! [remote rejected] master (pre-receive hook declined)