Hi, I've spent some time today migrating the old backport-conflict detection script from Buildbot[1] to GitHub Actions[2] (login required). It seems I finally got it going, this last job succeeded.
It would probably be interesting to try to nominate a known conflicting backport in STATUS to verify we get a proper notification but I'm out of time for today. With this, I've removed the old Buildbot job in r1089181 from the Infrastructure repo [3] We still have one job left in Buildbot, the svn-warnings job. (This is the job that alerted me of the unused variable removed in r1924107). I'd like to remove that as well, to reduce maintenance burden somewhat. Can we include the same functionality in one of the other jobs? Or should we just remove it? Cheers, Daniel [1] https://ci2.apache.org/#/builders [2] https://github.com/apache/subversion/actions [3] https://svn.apache.org/repos/infra/infrastructure/buildbot2/projects Den sön 2 mars 2025 kl 00:17 skrev GitBox <g...@apache.org>: > > The GitHub Actions job "backportbot" on subversion.git has succeeded. > Run started by GitHub user asfgit (triggered by asfgit). > > Head commit for run: > 5688bdcf04f402327e5134852b46a2d7bb99350c / Daniel Sahlberg < > dsahlb...@apache.org> > Followup to r1924124 and r1924122 > Merge r1924125 from trunk, switching to a proper SVN WC > > > > git-svn-id: > https://svn.apache.org/repos/asf/subversion/branches/1.14.x@1924127 > 13f79535-47bb-0310-9956-ffa450edef68 > > Report URL: https://github.com/apache/subversion/actions/runs/13609753381 > > With regards, > GitHub Actions via GitBox > >
