An error occurred fetching the project authors.
- 29 Jun, 2018 1 commit
-
-
Douwe Maan authored
-
- 20 Jun, 2018 1 commit
-
-
Alexis Reigel authored
-
- 15 Jun, 2018 1 commit
-
-
Douwe Maan authored
See https://gitlab.com/gitlab-org/gitlab-ce/issues/47677 for more information
-
- 11 Jun, 2018 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 08 Jun, 2018 1 commit
-
-
Douwe Maan authored
-
- 06 Jun, 2018 7 commits
-
-
Alexis Reigel authored
the ci status icons are generated client side, wo we don't need the static files anymore.
-
Alexis Reigel authored
the initial reason for this change was that graphicsmagick does not support writing to ico files. this fact lead to a chain of changes: 1. use png instead of ico (browser support is good enough) 2. render the overlays on the client using the canvas API. this way we only need to store the original favion and generate the overlay versions dynamically. this change also enables (next step) to simplify the handling of the stock favicons as well, as we don't need to generate all the versions upfront.
-
Alexis Reigel authored
this ways we can keep the `lib/gitlab/ci/status/*` classes to return the bare favicon name as it was before. also the favicon uploader versions are now have the same names as the stock favicons (+ `favicon_` prefix), which makes working with the status names easier.
-
Alexis Reigel authored
-
Alexis Reigel authored
Without the '?' at the end of the favicon url the custom favicon (i.e. the favicons that are served through `UploadController`) are not shown in the browser. It may have something to do with how `#send_file` / `#send_data` set http headers. When serving the same icon file from the public directory everything is fine.
-
Alexis Reigel authored
-
Alexis Reigel authored
-
- 05 Jun, 2018 7 commits
-
-
Alexis Reigel authored
the ci status icons are generated client side, wo we don't need the static files anymore.
-
Alexis Reigel authored
the initial reason for this change was that graphicsmagick does not support writing to ico files. this fact lead to a chain of changes: 1. use png instead of ico (browser support is good enough) 2. render the overlays on the client using the canvas API. this way we only need to store the original favion and generate the overlay versions dynamically. this change also enables (next step) to simplify the handling of the stock favicons as well, as we don't need to generate all the versions upfront.
-
Alexis Reigel authored
this ways we can keep the `lib/gitlab/ci/status/*` classes to return the bare favicon name as it was before. also the favicon uploader versions are now have the same names as the stock favicons (+ `favicon_` prefix), which makes working with the status names easier.
-
Alexis Reigel authored
-
Alexis Reigel authored
Without the '?' at the end of the favicon url the custom favicon (i.e. the favicons that are served through `UploadController`) are not shown in the browser. It may have something to do with how `#send_file` / `#send_data` set http headers. When serving the same icon file from the public directory everything is fine.
-
Alexis Reigel authored
-
Alexis Reigel authored
-