Hi, There used to be some problems related to CI. At least ASF Jenkins differentiates between forked PRs and non-forked PRs. For GitHub Actions there is a difference with regards to permissions (https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-permissions-for-github_token#changing-the-permissions-in-a-forked-repository) which might affect PR decoration and other stuff.
Are you sure that everything related to building PRs works just as well in forks? Konrad > On 4. Jan 2025, at 15:14, Tamás Cservenák <ta...@cservenak.net> wrote: > > Howdy, > > I'd like to ask devs to NOT code directly against branches in ASF > repositories, as we are swamped literally with unwanted spam: I am not > interested in each commit of the branch being worked on. > > Instead, fork the repo and create PRs. > > The commits ML is nearly unusable, I'd really like to see _only the > changes_ in "proper" codebases, but instead we have thousands of mails > about commits on any branch in there: > https://lists.apache.org/list.html?comm...@maven.apache.org > > This also raises the problem of branch cleanup in canonical reposes as well... > > TL;DR: fork and create PRs from forks please. > > Thanks, > T > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org >
