You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assumed that if we just had one it would show up for both "members" and "public". It now seems that if we want it to show up for "members" at all, we also need to have a private one.
If so, I propose we have a duplicate repo. I'd prefer a way that didn't require duplicate versions that would have the potential to inadvertently diverge, but I don't currently see a way to do that.
Hi @KirstieJane! I think the discussion on the-turing-way/the-turing-way#3282 gives the best background.
The summary is that we currently have two separate readmes with no functional difference, and it would be good if we didn't have to manually sync them. I expect there'll be a way to can make that happen but I don't have time right now to find one so I'm just making the issue for now.
It's also possible that GitHub might have tweaked it's implementation since that discussion to allow a way to just have one readme (since I expect that would be a frequent suggestion/request), but again I don't have time right now to look into that.
Thanks @da5nsy - I remember that from a year ago! Thank you for the link to the discussion.
What a truly ridiculous set up that GitHub has created!
Happy for this to stay open until someone (including maybe GitHub themselves - I just did a google and it doesn't seem like they've changed the behaviour yet) has time to fix.
One idea is to add a test to check to see if the two files are different and then the person making the change can copy over their edits to the other file. Still manual but at least checked at the time of the divergence?
the-turing-way/the-turing-way#3282 (comment):
...
The text was updated successfully, but these errors were encountered: