I am not sure what happened here but I was sure I had posted an update.
The issue with the merge request is that we are trying to change the composer.lock. At some point the composer.lock file needs to change but I think this should happen the next time Composer is run for Drupal Core. I am not sure what this process is. But the hashes in composer.lock are changing so this means that Composer is updating composer.lock at some point.
Thoughts about leaving out composer.lock from the MR?
Thanks,
Steve
@smustgrave, sorry for the basic question but I am trying to do the rebase I cannot find the correct name for the remote branch. I would think it should be origin/issue-3044974 but my local git client is reporting that the branch does not exist.
Thank you for the help.
Thanks,
Steve
Maks,
The plan had been to make these changes and then open a new ticket to make all of the changes in the files to include Markdown. I am fine either way. It is going to take me a bit to get all the Markdown changes made.
Thoughts?
Thanks,
Steve
Ready for review: https://git.drupalcode.org/project/drupal/-/merge_requests/8115
Thanks @koppie and @kristen-pol, for your help. I think I uploaded the wrong file last time because I know I made those changes.
Thanks,
Steve
This new patch should cover all the issues.
Thank you for the reviews and feedback.
This patch covers the changes above and adds the composer folder. The composer folder is only found when cloning the git directory rather than downloading with composer.
Third time is the charm.
Rerolled patch without /web
Rolled a new patch. Removed changes to composer.lock and other composer files.
I am at DrupalCon working on getting this patch in 22 to be applyable.
Adding @nmeshes short description so we can move to need review.
The provided short description is more than 200 characters. How about;
A developer module to assist with creating workflow states and transitions in code used to manage the lifecycle of an entity via states and transitions. Entities can have multiple workflows.
Just cleaning up the short description to make it better.
Making the short description better.
Updating the short description to meet length standards.
@heatherwoz, thanks for improving mine. It sounds good.
Thanks,
Steve
How about this:
This module creates a sitemap that conforms to the sitemaps.org specification. The module will help you automatically submit your generated sitemap to consumers like Google and Bing.
I was thinking the limit was 300 characters. Fixed for 200.
Completed at DrupalCon Pittsburg.
Work done at DrupalCon Pittsburg.
This was done at DrupalCon Pittsburgh.
Worked on at DrupalCon Pittsburgh.
This ticket was updated at DrupalCon Pittsburgh.
This was done at DrupalCon Pittsburgh.
Short Description
Allows for the exporting data from Drupal Views in formats such as CSV, Microsoft XLS, or Microsoft Doc.
This ticket was worked on at DrupalCon Pittsburgh.
Short Description
This module provides a tool allow content editors to add additional link tag attributes such as id, class, or target.
This was done for DrupalCon Pittsburgh.
Short Description
This module creates a sitemap that conforms to the sitemaps.org specification. Sitemaps are used by search engines like Google and Bing to support the crawling of websites. The module will help you automatically submit your generated sitemap.
This was done at DrupalCon Pittsburgh.
Short Description
This module allows for a Drupal entity such as an image or video to be inserted directly into the WYSIWYG editor.
Short Description:
Select a color to save as the value of a field. Allows for the value to be saved in multiple formats. Supports multiple methods for providing a user a simple way to select a color.
I have reviewed this in Drupal 9 and 10 at the DrupalCon contribution sprint and it looks good.