An error occurred fetching the project authors.
- 24 May, 2016 1 commit
-
-
Stan Hu authored
[ci skip]
-
- 23 May, 2016 6 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Stan Hu authored
Closes #17730
-
Grzegorz Bizon authored
-
Robert Speicher authored
[ci skip]
-
Robert Speicher authored
[ci skip]
-
- 22 May, 2016 5 commits
-
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
Grzegorz Bizon authored
-
Kamil Trzcinski authored
-
Grzegorz Bizon authored
-
- 21 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 20 May, 2016 3 commits
-
-
Alfredo Sumaran authored
-
Alfredo Sumaran authored
-
Jeroen Jacobs authored
-
- 19 May, 2016 5 commits
-
-
Kamil Trzcinski authored
-
Grzegorz Bizon authored
-
Ludovic Perrine authored
-
Sean McGivern authored
It's possible to construct a commit graph where the output of `git log` isn't in timestamp order. Grouping the commits in the list by date then gives dramatically wrong results. Instead, go for the more pragmatic approach: use the commits in the order they're given, and just show the date line each time the date changes. This means that the same date header can show up multiple times, but at least the ordering is preserved.
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 18 May, 2016 10 commits
-
-
Robert Schilling authored
-
Sean McGivern authored
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Adam Butler authored
-
Jeroen van Baarsen authored
-
Jeroen van Baarsen authored
-
Jeroen van Baarsen authored
Signed-off-by:
Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
Rémy Coutable authored
[ci skip] Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Alex Moore-Niemi authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Felipe Artur authored
-
- 17 May, 2016 1 commit
-
-
James Lopez authored
-
- 16 May, 2016 7 commits
-
-
Yorick Peterse authored
-
Felipe Artur authored
-
Felipe Artur authored
-
Felipe Artur authored
-
Felipe Artur authored
-
Sean McGivern authored
Before: we took the next milestone due across all projects in the search and found issues whose milestone title matched that one. Problems: 1. The milestone could be closed. 2. Different projects have milestones with different schedules. 3. Different projects have milestones with different titles. 4. Different projects can have milestones with different schedules, but the _same_ title. That means we could show issues from a past milestone, or one that's far in the future. After: gather the ID of the next milestone on each project we're looking at, and find issues with those milestone IDs. Problems: 1. For a lot of projects, this can return a lot of IDs. 2. The SQL query has to be different between Postgres and MySQL, because MySQL is much more lenient with HAVING: as well as the columns appearing in GROUP BY or in aggregate clauses, MySQL allows them to appear in the SELECT list (un-aggregated).
-
Sean McGivern authored
When an admin changes a user's password for them, force the user to reset the password after logging in by expiring the new password immediately.
-
- 15 May, 2016 1 commit
-
-
Pablo Carranza authored
-