Specify exact mappings for date fields in git documents

[Rafaeltheraven]

Simple PR, just specifies that AuthorDate and CommitDate are date fields in ES. This allows us to later do better filtering such as being able to specify AuthorDate <= {Some Date}.

[Rafaeltheraven]

Amended the commit message and made the tests pass is the rebase good like this? I must admit I am not very familiar with more "proper" advanced git techniques.

[coveralls]

Pull Request Test Coverage Report for Build 3948257475

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 82.313%

---

Totals
Change from base Build 3930924127:	0.02%
Covered Lines:	9103
Relevant Lines:	11059

---

💛 - Coveralls

[sduenas]

Amended the commit message and made the tests pass is the rebase good like this? I must admit I am not very familiar with more "proper" advanced git techniques.

You need to run the command git rebase -i master on the branch of this PR. The editor will open with a list of commits, for the 2nd o the last one, where it says pick replace it by an s(squash), and save the file. The editor will show again the messages you wrote for each commit. Remove everything and paste this:

[schema] Specify exact mappings for data fields in git documents

This allows us to later do better filtering such as
being able to specify AuthorDate <= {Some Date}.
Tests updated accordingly.

The format is compatible with ES6, using `MMM`
instead of `LLL` for the month section.

Signed-off-by: Rafael Dulfer <rafael.dulfer@gmail.com>

Save the file and git will squash your commits into a single one and your branch will be updated with the latest commits from master. Then, push the commits again to the branch on the remote repository with the option --force

[Rafaeltheraven]

Thanks for the guide! Took me a couple of tries, but it's all squashed now

[sduenas]

Thanks for the guide! Took me a couple of tries, but it's all squashed now

You almost did it :). Apparently, you didn't pull the latest commits from the master branch in your fork. I see that the last commit you have is 25c2895c - two months ago- . You have to sync your repo first.

I can do the rebase of your PR but I don't have permissions to write in your branch.

[Rafaeltheraven]

Oh yeah, those got destroyed in my rebasing adventure... After another fun adventure they're merged in now.

[sduenas]

@Rafaeltheraven thanks for your contribution! I successfully merged it. I hope you have learnt some new things with git :)