| /********************************************************************************* | |
| Copyright (c) 2019, Greg Lockwood | |
| All rights reserved. | |
| Redistribution and use in source and binary forms, with or without | |
| modification, are permitted provided that the following conditions are met: | |
| * Redistributions of source code must retain the above copyright notice, this | |
| list of conditions and the following disclaimer. |
| async loadCSSStyles(){ | |
| return new Promise((resolve, reject)=>{ | |
| const styleURLs = [...]; | |
| await Promise.all(styleURLs.map(async style => await fetchStyle(style))); | |
| resolve(); | |
| }) | |
| }) | |
| const fetchStyle = (url) => { | |
| //https://stackoverflow.com/questions/574944/how-to-load-up-css-files-using-javascript | |
| return new Promise((resolve, reject) => { |
This totally happened, y'all can stop +1ing this now. GitHub Blog post. Direct link to settings where you can set this.
#Per-organization / per-repo email overrides - A feature suggestion
Here the concepts "organization" and "user" are interchangeable, I'm talking about an entity that owns a repo, whether it is jQuery or John Resig. I'll stick to using organization as it best represents my original use-case.
##TL;DR
