docs: give files over 100 MB their route

CONTRIBUTING sent any file over the browser's 25 MB through a clone, which GitHub refuses past 100 MB, and named a release only a maintainer can write to. It now gives the route validate_pr.py prints: an issue with the hashes.
This commit is contained in:
Abdessamad Derraz committed 2026-11-05 19:18:38 +01:00
1 parent 46a6ac2675
commit 9e04bf887d
3 files changed
+20 -2

No files matched your search

+5 -1
View File
@@ -37,6 +37,7 @@ from common import (
from nativemode import check_label
import release_record
from siteguides import install_command
from validate_pr import LARGE_FILE_ISSUE_URL
from verify import verify_platform
@@ -930,7 +931,10 @@ the most useful contribution.
From a clone, the file goes to `bios/Manufacturer/Console/filename`, and
`python scripts/validate_pr.py path/to/file` names that folder for a file still
outside `bios/`. Given a folder, such as an old card's BIOS folder, it checks
every file under it. A file over the browser's 25 MB limit goes in that way.
every file under it. A file over the browser's 25 MB limit goes in that way,
up to the 100 MB GitHub accepts in a push. A larger file stays out of the pull
request: [open an issue]({LARGE_FILE_ISSUE_URL}) with the hashes
`validate_pr.py` prints, and a maintainer adds it to the `large-files` release.
## Add a platform