software-engineering-quality-framework
software-engineering-quality-framework copied to clipboard
🏎️ Shared best-practice guidance & tools to support software engineering teams
Temp PR: diff between blueprints branch and red lines branch
Not ready for review This is a possible way we might elevate some of our principles into a firmer position
Adding, to the contributions guide, a reference to the "Consider comments and Readme text" principle (in the "Create knowledge" chapter) (Also removed a couple of references to NHSD)
Over [here](https://github.com/NHSDigital/software-engineering-quality-framework/blob/22a93eb891ec959ece987bbdc9ab2cd3b6947bca/practices/securing-repositories.md?plain=1#L53), we say: ``` - Disable ability to push to the default branch for everyone, admins included (`applies-to-admin` option). ``` I'm not sure about the `default branch` wording. What...
https://github.com/NHSDigital/software-engineering-quality-framework/blob/3659ffdffb2e3f7d9fdad394575f1df378c79134/scripts/markdown-check-format.sh#L16 wants bumping to v0.39.0. That should squash the `punycode` deprecation warnings in the output.
Just a sanity check to see what the behaviour of the link checker is around redirects.
Consolidation of some, and deletion of what could be duplication