Thanks, now we have a pretty straightforward answer about that issue . Basically it’s not a bug but a design decision.
On the other hand it is kind of a usability issue. This behavior makes it impossible to have a “copy and paste” workflow configuration or a “fork and publish” repository that will just build a repository and publish it to Github’s web hosting without complex additional configuration. (Like it’s possible to do so with both Gitlab and Bitbucket as example.)
Is there any chance this usability problem could be considered by the dev team to create some kind of specific exception for static web content publishing?