summaryrefslogtreecommitdiff
path: root/tests/index/conflicts.c
Commit message (Collapse)AuthorAgeFilesLines
* introduce `git_index_entry_is_conflict`Edward Thomson2015-05-281-2/+2
| | | | | | | | | It's not always obvious the mapping between stage level and conflict-ness. More importantly, this can lead otherwise sane people to write constructs like `if (!git_index_entry_stage(entry))`, which (while technically correct) is unreadable. Provide a nice method to help avoid such messy thinking.
* conflict tests: use GIT_IDXENTRY_STAGE_SETEdward Thomson2015-05-281-10/+10
|
* index: validate mode of new conflictsEdward Thomson2015-05-281-1/+8
|
* conflicts: when adding conflicts, remove stagedEdward Thomson2015-05-281-0/+50
| | | | | | When adding a conflict for some path, remove the staged entry. Otherwise, an illegal index (with both stage 0 and high-stage entries) would result.
* Introduce cl_assert_equal_oidEdward Thomson2014-07-011-13/+13
|
* index: rename an entry's id to 'id'Carlos Martín Nieto2014-01-251-20/+20
| | | | This was not converted when we converted the rest, so do it now.
* Rename tests-clar to testsBen Straub2013-11-141-0/+287