Problem/Motivation

Replace README.txt with README.md

Steps to reproduce

Need README.md format

Proposed resolution

Fallow this format
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

Issue fork autologout-3315952

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:

Comments

dineshreddymathuku created an issue. See original summary.

immaculatexavier made their first commit to this issue’s fork.

immaculatexavier’s picture

Committed in accordance to the proposed resolution

immaculatexavier’s picture

Status: Active » Needs review
immaculatexavier’s picture

Committed that adheres to Drupal standards.

dineshreddymathuku’s picture

HI #5 thanks for your Responce

damienmckenna’s picture

Status: Needs review » Needs work

This is pretty good, but the "Contents of this file" section is not necessary.

gowthamrajkrishnasamy made their first commit to this issue’s fork.

immaculatexavier’s picture

Status: Needs work » Needs review

Committed in accordance to #8

gowthamrajkrishnasamy’s picture

Hi Damien,
Updated as per your suggestion

dineshreddymathuku’s picture

hi all Updated README.md file As per Markdown format
thanks

Manoj Raj.R made their first commit to this issue’s fork.

Manoj Raj.R’s picture

Committed according to the proposed solution.
As per #8.

Please review it

Pracheth’s picture

Status: Needs review » Reviewed & tested by the community

Reviewed #14(latest merge request updated 10 November 2022 ) by @Manoj Raj.R, README.md looks good to me and adheres to Drupal markdown practices.
Also, reflects the changes suggested in #8.

Changing the status to Reviewed and Tested by Community.

Manoj Raj.R’s picture

Updated according to the latest information from the Drupal ORG.

https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

DeaOm made their first commit to this issue’s fork.

deaom’s picture

Status: Reviewed & tested by the community » Needs review
Related issues: +#3363875: Autologout disabled after 1.4 Upgrade

The MR #27 can be closed as all the changes were happening in the MR #26. I added a FAQ section based on the #3363875: Autologout disabled after 1.4 Upgrade, ready for review.
I also suggest to the maintainers to update the documentation page, with adding the information regarding the updating from 1.3 to 1.4 so there is no confusion.

And also, test are expected to fail due to core issue related to migrations #3192893: [META] Serialization issues in Migration tests.

deaom’s picture

admirlju made their first commit to this issue’s fork.

rushikesh raval’s picture

Status: Needs review » Reviewed & tested by the community

I have reviewed MR!26. It is now as per drupal recommendation.
So moving it to RTBC

admirlju’s picture

Status: Reviewed & tested by the community » Needs review

Because js-cookie was deprecated in Drupal 10 and will be removed in Drupal 11 this module now depends on JS Cookie module. Add the requirements to the README.md

admirlju’s picture

Rebased so tests can pass on the MR26

deaom’s picture

Removed the Q&A that was added (by me) for the option to disable destination, as some other configuration changes will be added in the future and I think the first Q&A covers it with the configuration export (as all the new configuration features will be added to the new release), but did remove the to 1.4 in the Q as not sure what the new version will be, but basically applies for upgrading from 1.3 or 1.4 version. Maybe wording needs to be different for the Q (How to upgrade from version 1.3 to 1.4 or later?)? Not sure, so leaving it to needs review.

ressa’s picture

Thanks @DeaOm. Perhaps @gowthamrajkrishnasamy or someone with the right permissions can hide or delete the irrelevant branch 3315952-replace-readme.txt_to_readme.md?

deaom changed the visibility of the branch 3315952-replace-readme.txt_to_readme.md to hidden.

deaom’s picture

Rebased MR, as it's just a Readme file, it can be applied to 8x and 2x branch, but can't change the MR target branch.

the_g_bomb made their first commit to this issue’s fork.

the_g_bomb’s picture

Version: 8.x-1.x-dev » 2.x-dev

Rebased MR

the_g_bomb’s picture

Status: Needs review » Reviewed & tested by the community
inregards2pluto’s picture

Re the new release roadmap, I'm wondering if it makes since to address the other outstanding tickets first, THEN update this to reflect any new features added in?

the_g_bomb’s picture

Good idea

the_g_bomb’s picture

I've updated the README with details of some of the recent changes.

the_g_bomb’s picture

Status: Reviewed & tested by the community » Needs review
inregards2pluto’s picture

Status: Needs review » Reviewed & tested by the community

Reviewed changes. README.md is updated to reflect recently added features and bug fixes. Markdown and sections align with Drupal documentation at https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or....

Updating to RTBC.

the_g_bomb’s picture

Status: Reviewed & tested by the community » Fixed

Merged, thanks for the help

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.

ressa’s picture

Thanks everyone!

Perhaps the doc link under "Resources" on the project page can be updated?

It's always best to not define a branch version in such links, to not have to eternally update it. Hopefully, @the_g_bomb can get the "Maintainer"-role before too long, to allow updating the default GitLab branch to 2.x :)

Status: Fixed » Closed (fixed)

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