reorganize-docs branch status

[nicoddemus]

https://github.com/pytest-dev/pytest/commits/reorganize-docs is the branch that @obestwalter, @pfctdayelise, and @hackebrot worked during our 2016 sprint. This has been sitting there for two years now, and unfortunately may cause confusion because the docs are online and outdated (#4115 (comment)).

@obestwalter, @pfctdayelise, and @hackebrot, would you like to keep the branch or should we delete it? I'm not sure how useful the branch is, given that it is probably riddled with conflicts by now...

[blueyed]

given that it is probably riddled with conflicts by now...

Just two files when merging master:

CONFLICT (content): Merge conflict in doc/en/skipping.rst
CONFLICT (content): Merge conflict in AUTHORS

[nicoddemus]

Oh I'm surprised, hehehe!

[pfctdayelise]

I would say delete it 😑

[Zac-HD]

From a quick skim over the diff, it's mostly placeholder pages for the reorganization and the completed pages all cover content that has since been expanded (marks, xfail, skipping). I'd delete the branch.

[hackebrot]

I copied the branch to my fork. Go ahead and delete it @nicoddemus! 🗑

[nicoddemus]

Deleted then! As long as it is saved somewhere we can always get it back if we want to.

Thanks everyone! 🤗

[kini]

I found some pytest documentation pages on google which had "reorganize-docs" in their URLs (e.g. https://docs.pytest.org/en/reorganize-docs/new-docs/user/directory_structure.html). I couldn't find any explanation internal to the pages themselves as to why they exist, whether they're relevant / up to date, etc., so I went searching on github, which led me to this ticket.

Do those pages come from the branch being discussed in this github issue? If so, since the branch has been deleted, should the pages also be removed from the website?

[The-Compiler]

We've long deleted them, unfortunately they're still around somehow, and even a redirect didn't help. I'll get in contact with ReadTheDocs support to see if they can do something about it.

[The-Compiler]

FYI I have some news on this, see #8098.