Definitely move to GitHub and not create another workaround workflow to keep SVN alive. Tools drop SVN support (I think most already have), and just getting a working SVN client is not as easy as it should be (probably depends on platform).
> Am 17.06.2025 um 02:47 schrieb PJ Fanning <[email protected]>: > > I would support moving to git. > GitHub CI has started working on our GitHub mirror. For ages, only > commits to the trunk branch triggered jobs but now we are seeing PRs > lead to jobs triggering. > Our main CI jobs are on https://ci-builds.apache.org/ though. > >> On Mon, 16 Jun 2025 at 20:11, Dave Fisher <[email protected]> wrote: >> >> Hi Devs, >> >> Over the weekend I saw PJ was triaging some PRs from a contributor, and >> thought I would take a look at some of the older ones and do some triage. >> Because of the fact that GitHub.com/apache/poi is git mirror of svn I was >> unable to close these PRs. I can close these issues from a svn commit >> message: >> >> svn ci -m ‘closes #123, closes #345’ >> >> Here’s the GH docs about the commit message: >> https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword >> >> If there are no objections I’ll create a file called `.svn-gh-pr-closer`, >> append notes, and commit messages. >> >> The alternative would be to migrate over to GitHub. One prospective way to >> start would be to add CI workflows to GH. >> >> Best, >> Dave >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
