summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | cmake: move test enablement into test cmakeEdward Thomson2021-11-111-0/+2
| |_|/ |/| |
* | | Merge pull request #6104 from libgit2/ethomson/pathEdward Thomson2021-11-1178-955/+1002
|\ \ \ | | | | | | | | path: refactor utility path functions
| * | | path: length validation respecting core.longpathsEdward Thomson2021-11-091-18/+19
| | | | | | | | | | | | | | | | | | | | Teach `git_path_is_valid` to respect `core.longpaths`. Add helper methods to validate length and set the error message appropriately.
| * | | path: introduce `git_path_str_is_valid`Edward Thomson2021-11-091-7/+7
| | | | | | | | | | | | | | | | | | | | Add a `git_str` based validity check; the existing `git_path_is_valid` defers to it.
| * | | fs_path: make empty component validation optionalEdward Thomson2021-11-091-13/+30
| | | |
| * | | fs_path: introduce `str_is_valid`Edward Thomson2021-11-091-0/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide a mechanism for users to limit the number of characters that are examined; `git_fs_path_str_is_valid` and friends will only examine up to `str->size` bytes. `git_fs_path_is_valid` delegates to these new functions by passing `SIZE_MAX` (instead of doing a `strlen`), which is a sentinel value meaning "look for a NUL terminator".
| * | | path: `validate` -> `is_valid`Edward Thomson2021-11-091-68/+68
| | | | | | | | | | | | | | | | | | | | Since we're returning a boolean about validation, the name is more properly "is valid".
| * | | fs_path: `validate` -> `is_valid`Edward Thomson2021-11-091-133/+133
| | | | | | | | | | | | | | | | | | | | Since we're returning a boolean about validation, the name is more properly "is valid".
| * | | path: separate git-specific path functions from utilEdward Thomson2021-11-0978-952/+954
| |/ / | | | | | | | | | | | | | | | Introduce `git_fs_path`, which operates on generic filesystem paths. `git_path` will be kept for only git-specific path functionality (for example, checking for `.git` in a path).
* | | Add tests for ODB refreshJosh Triplett2021-11-086-7/+198
|/ / | | | | | | | | Add optional refreshing in the fake backend, and count the number of refresh calls if enabled.
* | libgit2_clar is now libgit2_testsMartin Kühl2021-10-282-5/+5
|/ | | | | | in #6083 the test runner was renamed to libgit2_tests, but not all references to the old name were updated. this change changes all of them to use the new name.
* cmake: stylistic refactoringEdward Thomson2021-10-181-49/+49
| | | | | Ensure that we always use lowercase function names, and that we do not have spaces preceding open parentheses, for consistency.
* cmake: BUILD_CLAR is now BUILD_TESTSethomson/clar_no_moreEdward Thomson2021-10-172-12/+12
| | | | | Nobody knows what CLAR is. The test building option should be `BUILD_TESTS`.
* str: introduce `git_str` for internal, `git_buf` is externalethomson/gitstrEdward Thomson2021-10-17192-2483/+2487
| | | | | | | | | | | | | | | | | | | | | | | | | | | libgit2 has two distinct requirements that were previously solved by `git_buf`. We require: 1. A general purpose string class that provides a number of utility APIs for manipulating data (eg, concatenating, truncating, etc). 2. A structure that we can use to return strings to callers that they can take ownership of. By using a single class (`git_buf`) for both of these purposes, we have confused the API to the point that refactorings are difficult and reasoning about correctness is also difficult. Move the utility class `git_buf` to be called `git_str`: this represents its general purpose, as an internal string buffer class. The name also is an homage to Junio Hamano ("gitstr"). The public API remains `git_buf`, and has a much smaller footprint. It is generally only used as an "out" param with strict requirements that follow the documentation. (Exceptions exist for some legacy APIs to avoid breaking callers unnecessarily.) Utility functions exist to convert a user-specified `git_buf` to a `git_str` so that we can call internal functions, then converting it back again.
* hash: hash functions operate on byte arrays not git_oidsEdward Thomson2021-10-025-9/+9
| | | | | | Separate the concerns of the hash functions from the git_oid functions. The git_oid structure will need to understand either SHA1 or SHA256; the hash functions should only deal with the appropriate one of these.
* hash: accept the algorithm in inputsEdward Thomson2021-10-015-7/+7
|
* Merge pull request #6076 from libgit2/ethomson/oidarray_disposeEdward Thomson2021-09-271-37/+37
|\ | | | | oidarray: introduce `git_oidarray_dispose`
| * oidarray: introduce `git_oidarray_dispose`ethomson/oidarray_disposeEdward Thomson2021-09-261-37/+37
| | | | | | | | | | | | Since users are disposing the _contents_ of the oidarray, not freeing the oidarray itself, the proper cleanup function is `git_oidarray_dispose`. Deprecate `git_oidarray_free`.
* | Merge pull request #6075 from libgit2/ethomson/attr_longpathsEdward Thomson2021-09-271-3/+3
|\ \
| * | attr_file: don't take the `repo` as an argethomson/attr_longpathsEdward Thomson2021-09-261-3/+3
| |/ | | | | | | The `repo` argument is now unnecessary. Remove it.
* | Merge pull request #6073 from libgit2/ethomson/attr_lookupsEdward Thomson2021-09-271-1/+88
|\ \
| * | repository: improve `hashfile` for absolute pathsEdward Thomson2021-09-251-1/+88
| |/ | | | | | | | | | | | | | | | | | | | | | | | | When `git_repository_hashfile` is handed an absolute path, it determines whether the path is within the repository's working directory or not. This is necessary when there is no `as_path` specified. If the path is within the working directory, then the given path should be used for attribute lookups (it is the effective `as_path`). If it is not within the working directory, then it is _not_ eligible. Importantly, now we will _never_ pass an absolute path down to attribute lookup functions.
* | buf: common_prefix takes a string arrayethomson/strarrayEdward Thomson2021-09-261-22/+7
|/ | | | | | `git_strarray` is a public-facing type. Change `git_buf_text_common_prefix` to not use it, and just take an array of strings instead.
* Merge pull request #6067 from libgit2/ethomson/filter_commit_idEdward Thomson2021-09-211-8/+2
|\ | | | | filter: use a `git_oid` in filter options, not a pointer
| * filter: use a `git_oid` in filter options, not a pointerethomson/filter_commit_idEdward Thomson2021-09-211-8/+2
| | | | | | | | | | | | | | Using a `git_oid *` in filter options was a mistake; it is a deviation from our typical pattern, and callers in some languages that GC may need very special treatment in order to pass both an options structure and a pointer outside of it.
* | rebase: fix (deprecated) signing testethomson/deprecationEdward Thomson2021-09-211-7/+7
|/
* Merge pull request #6061 from libgit2/ethomson/emailEdward Thomson2021-09-202-1/+383
|\ | | | | Introduce `git_email_create`; deprecate `git_diff_format_email`
| * diff: deprecate diff_format_emailethomson/emailEdward Thomson2021-09-181-0/+20
| | | | | | | | `git_diff_format_email` is deprecated in favor of `git_email_create`.
| * email: include renames by defaultEdward Thomson2021-09-181-2/+115
| | | | | | | | | | `git format-patch` includes diffs with rename detection enabled by default when creating emails. Match this behavior.
| * email: include binary diffs by defaultEdward Thomson2021-09-181-0/+53
| | | | | | | | | | `git format-patch` includes binary diffs by default when creating emails. Match this behavior.
| * email: allow `git_diff_commit_as_email` to take 0 as patch indexEdward Thomson2021-09-181-1/+0
| | | | | | | | | | Allow a `0` patch index and `0` patch count; in this case, simply don't display these in the email.
| * email: introduce `git_email_create_from_diff`Edward Thomson2021-09-181-13/+47
| | | | | | | | | | | | | | | | | | Introduce a function to create an email from a diff and multiple inputs about the source of the diff. Creating an email from a diff requires many more inputs, and should be discouraged in favor of building directly from a commit, and is thus in the `sys` namespace.
| * email: introduce `git_email_create_from_commit`Edward Thomson2021-09-181-0/+163
| | | | | | | | | | | | Create `git_email_*` which will encapsulate email creation and application, and `git_email_create_from_commit` in particular, which creates an email for a single commit.
* | Merge branch 'sathieu/patch-1' into mainEdward Thomson2021-09-201-0/+9
|\ \
| * | httpproxy: move empty string test above configEdward Thomson2021-09-201-4/+9
| | | | | | | | | | | | | | | The configuration change will override the environment variable, so the environment variable check needs to come first.
| * | Add test to ensure empty proxy env behaves like unset envMathieu Parent2021-09-141-0/+4
| | | | | | | | | Signed-off-by: Mathieu Parent <math.parent@gmail.com>
* | | win32: ensure content filtering occurs in longpath testEdward Thomson2021-09-201-4/+23
| | |
* | | Merge remote-tracking branch 'mathworks/longpath_filter_bug' into mainEdward Thomson2021-09-201-4/+24
|\ \ \
| * | | Apply suggestions from code reviewLaurence McGlashan2021-09-141-0/+2
| | | | | | | | | | | | Co-authored-by: Edward Thomson <ethomson@github.com>
| * | | Refactor shared code in longpath test.Laurence McGlashan2021-09-141-22/+12
| | | |
| * | | If longpaths is true and filters are enabled, pass git_repository through ↵Laurence McGlashan2021-09-141-0/+28
| |/ / | | | | | | | | | | | | | | | the filtering code to ensure the cached longpath setting is returned. Fixes: #6054
* | | Merge pull request #6058 from mathworks/proxy_config_with_detached_remoteEdward Thomson2021-09-201-1/+41
|\ \ \ | | | | | | | | Allow proxy options when connecting with a detached remote.
| * | | Update formatting.Laurence McGlashan2021-09-161-3/+3
| | | |
| * | | Allow proxy options when connecting with a detached remote.Laurence McGlashan2021-09-161-1/+41
| | |/ | |/|
* | | Add test for revert+rename bug.Colin Stolley2021-09-159-0/+60
|/ /
* | Merge pull request #6031 from libgit2/ethomson/extensionsEdward Thomson2021-09-143-42/+118
|\ \ | | | | | | Support custom git extensions
| * | common: support custom repository extensionsethomson/extensionsEdward Thomson2021-09-042-0/+74
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow users to specify additional repository extensions that they want to support. For example, callers can specify that they support `preciousObjects` and then may open repositories that support `extensions.preciousObjects`. Similarly, callers may opt out of supporting extensions that the library itself supports.
| * | repo: refactor extensions tests into their own fileEdward Thomson2021-09-032-42/+44
| |/
* | Add test config parsingBasile Henry2021-09-092-0/+12
|/ | | | | This tests parsing a multiline string containing multiple quoted comment chars. See #6019
* remote: refactor proxy detectionEdward Thomson2021-09-013-101/+139
| | | | | | | | | | Update the proxy detection for a remote. 1. Honor `http.<url>.proxy` syntax for a remote's direct URL and parent URLs. 2. Honor an empty configuration URL to override a proxy configuration. Add tests to ensure that configuration specificity is honored.
View Lorry Controller Status