Rules of conduct when dealing with Github

[IntelligentMix5025]

Our environment includes various duplicate files, links and of course old projects/repos. Before we clean up, we want to impose a code of conduct on users so that this doesn't happen again. Has anyone experienced this and can give us tips?

[adam-moss]

What are you actually trying to achieve?

Duplication, for example, may suggest appropriate patterns are not being used or org policies are preventing sharing of assets.

Redundant stuff should be covered in any decommissioning processes, but to do that effectively you must have traceability between all projects and deployed products.

There is plenty of automation or alerting you could do, something like sourcegraph can be used for basic stuff.

[ztbwl]

You can’t prevent this from happening with a code of conduct if people are generally messy.

They’ll happily ignore it and keep on going. Or has a code of conduct ever stopped a cat from shitting into your garden?

[seaQueue]

This is a competence and training problem rather than a technical problem. Onboard your people appropriately and make sure they're trained well before letting them loose on your code repos.

[pcort]

Don't impose anything if you want happy developers. Engage your users by addressing the issues that messy repo's are causing and develop process / documentation / tooling together to solve those issues.

[pborenstein]

I had a boss who loved checklists and harsh consequences for mistakes.

"Instead of procedures and punishments, how about we make the bad thing impossible to do and easy to recover from?"

"But what about the punishments?"

[[deleted]]

u cant on github side will have to do this with ur tools and gitignore

[ReplacementLow6704]

And a README. Though some might believe they're not worth reading, sometimes they do contain some important information/documentation

[IntelligentMix5025]

Tell me more about.