You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working on pretenders I wanted to steal a lot of things from deploystream.
eg. deassign-issue, pr-for-issue scripts, plus in time the get_dependencies.py for bower and npm modules.
And I'm sure the list will grow.
I'm wondering whether it makes sense to begin having a tools/scripts/something repo that could be updated centrally and shared between the two projects.
The text was updated successfully, but these errors were encountered:
Anyday soon I would like to start a specific repo for the front-end dependency management. We are using it at Rockabox and are making some improvements there as well, and it has great potential for proper packaging.
In my view of it, I'd like to end up with a single configuration file for multi-tool dependency management that looks sthg like:
(I have a script that downloads web fonts from FontSquirrel, I will improve it to unpack and install fonts to the appropriate locations in a similar way to bower).
I am planning to call it webdeps (if I leave the python stuff out, since with pip we can do requirements inheritance which I am not planning to here, or maybe I take a second look at how tox does that) or multideps.
As per the other stuff, it can be a separate repo.
When working on
pretenders
I wanted to steal a lot of things fromdeploystream
.eg. deassign-issue, pr-for-issue scripts, plus in time the
get_dependencies.py
for bower and npm modules.And I'm sure the list will grow.
I'm wondering whether it makes sense to begin having a tools/scripts/something repo that could be updated centrally and shared between the two projects.
The text was updated successfully, but these errors were encountered: