Problem/Motivation

Add README.md file which will help developer to know about the module while using the module.

Steps to reproduce

Proposed resolution

Follow Document to create file README Template

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork taxonomy_protect-3372726

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

dineshkumarbollu created an issue. See original summary.

dineshkumarbollu opened merge request !1

dineshkumarbollu’s picture

dineshkumarbollu commented
Assigned: dineshkumarbollu » Unassigned
Status: Active » Needs review
Bushra Shaikh’s picture

Bushra Shaikh commented
Status: Needs review » Needs work

I applied MR !1 got below error:

error: patch failed: src/Form/TaxonomyProtectAdminSettingsForm.php:1
error: src/Form/TaxonomyProtectAdminSettingsForm.php: patch does not apply
error: patch failed: taxonomy_protect.info.yml:1
error: taxonomy_protect.info.yml: patch does not apply
error: patch failed: taxonomy_protect.install:8
error: taxonomy_protect.install: patch does not apply
error: patch failed: taxonomy_protect.module:1
error: taxonomy_protect.module: patch does not apply
jrb’s picture

jrb
he/him
Primary language English
Location Raleigh-Durham Area, NC, USA
commented

If you just want to use this module, there's no need to apply this patch.

Mohd Sahzad made their first commit to this issue’s fork.

Mohd Sahzad opened merge request !2

  • jrb committed 660cd63d on 2.1.x 
    task: #3372726 Add README.md file

By: dineshkumarbollu
By: jrb
By:...
jrb’s picture

jrb
he/him
Primary language English
Location Raleigh-Durham Area, NC, USA
commented
Status: Needs work » Fixed
Issue tags: -

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.