Update README.md for Migrate Skip Fields

Created on 26 October 2023, about 1 year ago
Updated 21 August 2024, 4 months ago

Problem/Motivation

The README.md doesn't follow the pattern in the README.md template .

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Needs work

Version

1.0

Component

Documentation

Created by

🇩🇰Denmark ressa Copenhagen

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

Merge Requests

Comments & Activities

  • Issue created by @ressa
  • Merge request !1Update README.md → (Open) created by ressa
  • Status changed to Needs review about 1 year ago
  • 🇩🇰Denmark ressa Copenhagen
  • 🇩🇰Denmark ressa Copenhagen

    Cool module, thanks for making it!

  • Status changed to Needs work about 1 year ago
  • 🇵🇭Philippines kenyoOwen

    Hi ressa

    I reviewed your changes in MR!1 and the "Project name and introduction" is missing "Project page and issue queue links" and requirements section should follow README.md format

    ## Requirements
    
    This module requires the following modules:
    
    - [Views](https://www.drupal.org/project/views)
    - [Panels](https://www.drupal.org/project/panels)

    Thank you.

  • Status changed to Needs review about 1 year ago
  • 🇩🇰Denmark ressa Copenhagen

    Sure, let's add links to project and issue queue, but since there is only one module, we shouldn't use a list.

    PS. There's no need to change the Priority.

  • Status changed to RTBC about 1 year ago
  • 🇵🇭Philippines kenyoOwen

    Hi ressa

    I noticed extra spacing between the introduction and project page so I removed it. And it now follows the README.md template.

    Thank you.

  • Status changed to Needs work 4 months ago
  • 🇳🇮Nicaragua dinarcon

    Thanks for the MR. As of the latest release, the content MR is no longer accurate. Some notes:

    • The dependency on the migrate_upgrade module has been removed.
    • A new required migrate_skip_fields_source_version setting has been introduced.
    • The example of Radioactivity not offering an upgrade path is technically accurate, but the reference issue is about upgrading from Drupal 6 to Drupal 7. Can you file an issue for upgrading from Drupal 6/7 to Drupal 10/11? Then, we can link to the new issue. Or we could find a different module to use as example.

    Setting back to needs work.

Production build 0.71.5 2024