Sorting by GitHubUpdatedAt field

[himankpathak]

Description of the Change

Added GitHubUpdatedAt field which is fetched from GitHub's GraphQL API "updatedAt". It is stored in database at column GitHubUpdatedAt.

Benefits

Now issues can be sorted using GitHubUpdatedAt field.

Applicable Issues

Closes #5
Closes #7
Closes #12

[himankpathak]

@alexdor should a new issue be opened in the frontend to sort using GitHubUpdatedAt field?

[alexdor]

Looking good : ) Could you also set the GithubUpdateAt field as the default sorting for queries?

[alexdor]

@alexdor should a new issue be opened in the frontend to sort using GitHubUpdatedAt field?

Yes, once this is merged we should do that : )

[alexdor]

@himankpathak this still has conflicts, could you resolve the conflicts?

[himankpathak]

I think I resolved all the conflicts with git rebase. The PR says "This branch has no conflicts with the base branch".
Am I missing something?

[alexdor]

I'm getting this error so I don't think they where solved, you can try creating a new fork and cherry-picking your commits to that one

[himankpathak]

This is weird, on my side I don't know why it's not showing the conflicts.

Should I close this PR and make a copy of this branch from commit cd0f7ef and add commit d6f1492?

[alexdor]

Yeah, try creating a new pr, maybe that will solve the issue. Before you copy the branch, try just closing this pr and opening a new one, maybe it’s a GitHub issue that it shows conflicts Best, Alex

…

On 7 Oct 2019, 06:16 +0200, Himank Pathak ***@***.***>, wrote: This is weird, on my side I don't know why it's not showing the conflicts. Should I close this PR and make a copy of this branch from commit cd0f7ef and add commit d6f1492? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.