While I was reading #362, marked as bug, I felt that the PR was a bit of a bolt-on to something that is a workaround to missing Gitea functionality.
Isn't the issue really that Codeberg - with Gitea lacking a Github-like Pages feature of its own (i.e. with repo Settings UI for Pages) - came up with the workaround to have a "Pages" magic name to demarkate Pages repositories?
A possible solution being to turn the Codeberg Pages functionality in, idk, a Gitea plugin project maybe, offered on awesome-gitea, so its available all across the (gitea-)board, and for more people to add contrib?
Then other open issues (e.g. #303#218#115) with pending/proposed features can be addressed in that project.
While I was reading #362, marked as bug, I felt that the PR was a bit of a bolt-on to something that is a workaround to missing Gitea functionality.
Isn't the issue really that Codeberg - with Gitea lacking a Github-like Pages feature of its own (i.e. with repo Settings UI for Pages) - came up with the workaround to have a "Pages" magic name to demarkate Pages repositories?
A possible solution being to turn the Codeberg Pages functionality in, idk, a Gitea plugin project maybe, offered on [awesome-gitea](https://gitea.com/gitea/awesome-gitea), so its available all across the (gitea-)board, and for more people to add contrib?
Then other open issues (e.g. #303 #218 #115) with pending/proposed features can be addressed in that project.
As a maintainer of gitea I see the codebase grow and grow - at some moint it's hard to maintain and keep clean ... or just say it in other words: I dont like to see gitea to become gitlab
As a maintainer of gitea I see the codebase grow and grow - at some moint it's hard to maintain and keep clean ... or just say it in other words: I dont like to see gitea to become gitlab
100% valid point. I think my first sentence may have put you off-track.. sorry, should have formulated better, because in your 1st follow-up comment was what I intended: a side-project and/or plugin that exists independent of Gitea main project, and that people just grab iif they want a Pages-like service.
100% valid point. I think my first sentence may have put you off-track.. sorry, should have formulated better, because in your 1st follow-up comment was what I intended: a side-project and/or plugin that exists independent of Gitea main project, and that people just grab iif they want a Pages-like service.
While I was reading #362, marked as bug, I felt that the PR was a bit of a bolt-on to something that is a workaround to missing Gitea functionality.
Isn't the issue really that Codeberg - with Gitea lacking a Github-like Pages feature of its own (i.e. with repo Settings UI for Pages) - came up with the workaround to have a "Pages" magic name to demarkate Pages repositories?
A possible solution being to turn the Codeberg Pages functionality in, idk, a Gitea plugin project maybe, offered on awesome-gitea, so its available all across the (gitea-)board, and for more people to add contrib?
Then other open issues (e.g. #303 #218 #115) with pending/proposed features can be addressed in that project.
I'm personaly against this.
It should be a side project or eaven better implemented as a plugin
Part of Gitea then, ideally, you mean to say.. or just as-is?
Edit: I mentioned Plugin. Not familiar with all the packaging options at hand.
As a maintainer of gitea I see the codebase grow and grow - at some moint it's hard to maintain and keep clean ... or just say it in other words: I dont like to see gitea to become gitlab
100% valid point. I think my first sentence may have put you off-track.. sorry, should have formulated better, because in your 1st follow-up comment was what I intended: a side-project and/or plugin that exists independent of Gitea main project, and that people just grab iif they want a Pages-like service.