Commit Graph

5 Commits

Author SHA1 Message Date
Tianon Gravi a9d10c1219 Fix some "naughty" typos/bugs 2023-02-17 13:04:45 -08:00
Tianon Gravi 79a269637f Add support for "Builder: oci-import" in diff-pr
Also, update other scripts to use `bashbrew fetch` and `gitCache` effectively to remove unnecessary reimplementations of `BASHBREW_CACHE` default value calculation (new in bashbrew v0.1.8).

As a parting gift, add the raw list of total supported architectures to a file so it's more obvious when new ones are added or removed (like `ubuntu` losing `riscv64`).
2023-02-15 13:22:05 -08:00
Joe Ferguson a6b189f0c5 Add check to naughty-commits to ensure that referenced commit exists in the upstream GitFetch branch
Also update single-line library files to rfc2822 format to avoid 'refs/heads/*'
2021-10-08 16:09:46 -07:00
Tianon Gravi 79f67f8010 Fix Bash 4.3 issue and make scripts fail appropriately for similar issues in future 2020-02-11 15:36:06 -08:00
Tianon Gravi beb9e4a440 Add script to detect "naughty" commit histories
I originally wanted this script to be more generic and look for *any* modified binary files that are over a certain threshold, but it took ~88 minutes to run over the entire library, and almost all that time was spent in `git` itself generating commit diffs (since they're not stored on-disk in such a way that those commit diffs are inexpensive to calculate).

I also did a rough prototype in Go using https://github.com/src-d/go-git but it had essentially the same speed (as expected, since it's the underlying data that makes it expensive to calculate, not the language being used to request the data).

So, instead this looks for modified files which match `**.tar**`, which should match the ones we typically worry about anyhow (there are some other problematic cases, but they aren't going to be rebased anytime soon because they've been problematic for so long so aren't worth bending over backwards to detect).
2020-02-07 17:00:54 -08:00