1) There is single PITFILE that contains all tasks (which means that it would be source of conflicts in all task-related commits).
2) PITFILE contains tasks for all your projects instead of the current one, which means that it isn't really good candidate for storing inside your project's repository. This could be worked-around by exporting PITFILE every now and then, but it's far from perfect.
If you wan to make it useful then I would propose:
1) Store tasks inside git repository (maybe special refs/tasks/* tree? Like for tags or notes: refs/tags/* , refs/notes/*).
2) Store each task in separate file, that is: .git/refs/tasks/001, .git/refs/tasks/002, etc.
1) There is single PITFILE that contains all tasks (which means that it would be source of conflicts in all task-related commits).
2) PITFILE contains tasks for all your projects instead of the current one, which means that it isn't really good candidate for storing inside your project's repository. This could be worked-around by exporting PITFILE every now and then, but it's far from perfect.
If you wan to make it useful then I would propose:
1) Store tasks inside git repository (maybe special refs/tasks/* tree? Like for tags or notes: refs/tags/* , refs/notes/*).
2) Store each task in separate file, that is: .git/refs/tasks/001, .git/refs/tasks/002, etc.