(Assumed) Idea:
- Allow to manage WordPress.org assets through the git repository.
Resources
- Branch
bftrick by @BFTrick contains a simple mechanism to "overwrite everything in WP /assets with a magic directory name in git."
- Branch
cubetech by @cubetech contains a limited but focused mechanism to sync banner-* image files from the git root to svn assets.
Both approaches aren't really perfect, since kinda arbitrary. However, with regard to the goal of completely hiding away ugly svn operations for git developers, there is a point for doing so.
Discuss. :)
(Assumed) Idea:
Resources
bftrickby @BFTrick contains a simple mechanism to "overwrite everything in WP /assets with a magic directory name in git."cubetechby @cubetech contains a limited but focused mechanism to syncbanner-*image files from the git root to svn assets.Both approaches aren't really perfect, since kinda arbitrary. However, with regard to the goal of completely hiding away ugly svn operations for git developers, there is a point for doing so.
Discuss. :)