Contrib.social

What criterea is used to add to an existing automated fix issue?

Open on Drupal.org →
Created on 15 September 2022, over 2 years ago
Updated 4 March 2024, about 1 year ago

Problem/Motivation

Currently it is documented that it must be tagged ProjectUpdatBotD10 and have status [Active|Needs work|Needs review]
Wonder whether the following circumstances have an effect:

- The version is no longer the one reported originally.

- The project has commits about core_version_requirement supporting D10

- The project released a version supporting D10 (among earlier versions)

Steps to reproduce

NA

Proposed resolution

Depends on the answers

Remaining tasks

Depends on the answers

User interface changes

Depends on the answers

API changes

Data model changes

💬 Support request
Status

Postponed: needs info

Component

Code

Created by

🇳🇱Netherlands mmjvb

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment over 1 year ago →
    🇭🇺Hungary Gábor Hojtsy Hungary

    The code was moved to the project_analysis project, so you can review the codebase to get answers for these questions (and more!). Moving the issue there.

  • Status changed to Postponed: needs info about 1 year ago
  • Comment about 1 year ago →
    🇳🇱Netherlands bbrala Netherlands
    1. It checkes all issues by user id on the project
    2. then checks if tagged correctly.
    3. then checks uploaded files.
    4. does a diff to see if the patch files are same or not.
    5. if not, post patch/mr.

    So versions and such don't really matter.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024