This makes for perfect timing, I was just about to write some code to autopublish the distribution files for my project.
Where is a good place to put the output of a build these days? I really hate the idea of build artifacts in my repository cluttering every commit.
Push them to a downloads branch? its nice because it has versioning and can match the masters tags etc, but gh-pages has taught me I really dont like using branches as completely seperate repositories.
The size isnt a particular worry, this is a JavaScript library that should be producing small files.
s3 is another service to manage which is annoying, but it probably is the best option.
It is a shame, I do appreciate Github needs to focus on what is important, but this change stopped it from being a one stop shop for quite a few OS projects.
Where is a good place to put the output of a build these days? I really hate the idea of build artifacts in my repository cluttering every commit.
Push them to a downloads branch? its nice because it has versioning and can match the masters tags etc, but gh-pages has taught me I really dont like using branches as completely seperate repositories.