vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
1.7 KiB
Policies on git repositories
This document explains our current policies around git repositories. Everything not covered in this document is most likely a case-by-case decision. In these cases please create an issue with the Infrastructure Working Group.
New GitHub repositories
Requirements for new repositories as part of the LLVM organisation on GitHub:
- The repo will be used for something related to the LLVM ecosystem or community.
- The repo contains a
README.mdexplaining the contents. - The repo contains a
CONTRIBUTING.md, ideally copy this from llvm-project. - The repo contains a
LICENSE.TXT, preferably copy this from llvm-project. Other licences need to be discussed case-by-case.
If you want to integrate your project as part of the Monorepo, please take a look at the [Developer Policy](project:DeveloperPolicy.rst#Adding an Established Project To the LLVM Monorepo).
To request a new repository, please create an issue with the Infrastructure Working Group.
Repo access on GitHub
Some 3rd party applications require write access to our GitHub organisation in order to work properly. Typical examples are continuous integration services reporting build results back to GitHub. We consider granting access to such application if they provide benefits to the LLVM community and do not raise privacy or security concerns.
To request access please run an RFC on the mailing list and get community feedback.