Project Update Bot created MR against a 4.x branch from Drupal 4 - last commit 18 years ago

Created on 31 May 2024, 10 months ago
Updated 7 June 2024, 10 months ago

Problem/Motivation

The Project Update Bot created MR against a 4.x branch of Scheduler, which was for Drupal 4 - last commit 18 years ago, in 2006

Steps to reproduce

See https://git.drupalcode.org/project/scheduler/-/merge_requests/141
There were no commits added.

πŸ› Bug report
Status

Active

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom jonathan1055

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @jonathan1055
  • πŸ‡ΊπŸ‡ΈUnited States nicxvan

    That's optimistic!

  • πŸ‡¬πŸ‡§United Kingdom jonathan1055

    yes :-)

    I was wondering now that contrib projects can use semantic version numbering, they can appear to clash with very old core compatibility branches. Scheduler has 4.4.x-1.x and 5.x-1.x branch. The current 'latest' is now 2.x but when I want to create a 3.x branch then a 4.x branch it might start getting confusing. But I think the policy on drupal.org is never to delete a branch.

  • πŸ‡³πŸ‡±Netherlands bbrala Netherlands

    Pff. yeah the branch resolution is sometimes very hard, there are many weird options there :(

Production build 0.71.5 2024