-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #4: timestamp field #38
Merged
Merged
Conversation
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
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 8, 2023 14:15
8720b14
to
42d506c
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
2 times, most recently
from
December 9, 2023 09:44
6ef8e3f
to
cd95e27
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
2 times, most recently
from
December 14, 2023 09:47
fbd2a64
to
9834af7
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 14, 2023 10:09
9834af7
to
715edb7
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
2 times, most recently
from
December 14, 2023 16:53
4e7a873
to
376441f
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 14, 2023 16:54
376441f
to
ae3d633
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 16, 2023 12:56
be2fd3f
to
a76afb5
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
2 times, most recently
from
December 16, 2023 13:05
dc51b84
to
2141af1
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 16, 2023 13:07
2141af1
to
022d331
Compare
fmassot
reviewed
Dec 16, 2023
idrissneumann
force-pushed
the
feat_timestamp_field
branch
2 times, most recently
from
December 22, 2023 14:34
c2e2ff4
to
89226d0
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 22, 2023 14:55
89226d0
to
bc63730
Compare
fmassot
reviewed
Dec 27, 2023
fmassot
requested changes
Dec 27, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're good, I did not find issues while testing it.
Can we add a few tests on the backend side? This will really help to sleep at night :)
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 28, 2023 12:03
68e2b2f
to
71806e8
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 28, 2023 12:06
71806e8
to
26c22f5
Compare
idrissneumann
force-pushed
the
feat_timestamp_field
branch
from
December 28, 2023 12:07
26c22f5
to
1d64540
Compare
It's done :) |
fmassot
approved these changes
Dec 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.