-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
git: accept explicit commit hash for git context (#1765)
* git: accept explicit commit hash for git context When checking out code from non-github repositories, the typical assumptions may not be valid, e.g. that the only interesting non-branch commits have ref names starting with refs/pull. A specific example is fetching an un-merged commit from a gerrit repository by commit hash. This change just looks at the second part of the git context path and checks if it's a SHA commit hash, and if so, will fetch and check out this commit after cloning the repository. Sample context argument: https://github.repo/project#e1772f228e06d15facdf175e5385e265b57068c0 * ci: fix test script to recognize any non-zero exit as an error hack/linter.sh didn't properly install golangci-lint in hack/bin as I already have another version of golangci-lint on my PATH, but then it failed to execute because it was looking for it specifically in hack/bin. When the executable is not found, the exit code is 127 instead of 1, and so test.sh ignored the error. Two fixes: 1. `test.sh`: - Use `if (script) ...` instead of assigning / checking a result variable to determine if each validation script passed or failed. 2. `hack/linter.sh`: - Instead of checking for golangci-lint on the path, just specifically check for an executable file (`test -x`) in the expected location. Co-authored-by: Wade Carpenter <wwade@users.noreply.github.com>
- Loading branch information
Showing
4 changed files
with
102 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters