Add README.txt or something for locally cloned wikis

[spenserblack]

Discussed in #46

^{Originally posted by jcbhmr March 22, 2023}
I just had the random thought to include some kind of a file that would not be visible on github but would be if you cloned the wiki locally to say "heyyyy checkout the github repo instead, don't put stuff in the wiki here!"

similar idea i had just now while writing this would be to prepend a <!-- DO NOT EDIT ON PUBLISHED WIKI, ONLY EDIT IN SOURCE REPO -->\n or similar comment to all .md files to discourage editing the published version?

these ideas are kinda redundant if the user sees the "github-actions[bot] edited this" thing though... 🤷‍♀️

[spenserblack]

This seems like a potentially valid idea, but right now it's not a high priority IMO, so I'm adding the "icebox" label. If this gets interest from the community, I'll remove the label.

[jcbhmr]

offtopic

btw i think github projects was designed for this idea of "priority" stuff, while labels are intended to "categorize"?

maybe not tho cause here's a demo that uses projects to categorize. https://github.com/git-lfs/git-lfs/projects/3
but wait! here's the builtin template that is for priority (ish) since it uses a "backlog" and then other actively-working-on categories

[spenserblack]

Yeah, I was considering creating a project, but then I felt that it was a bit of overkill for this repo. Right now a simple issue list is plenty IMO.

But, you're right, projects are great for this sort of thing 🙂

[jcbhmr]

offtopic

now that im thinking about it from like 3 weeks in the future; i think this is exactly what the ideas discussions are for! you can leave a discussion "open" and it's like a proposal idea in stasis for an indefinite time (until a robot github workflow action closes it after 30 days or whatever if that's configured)

just a thought