Travis: check-in build files about carbon-icons

[hellobrian]

Npm publish is done. Need more time to figure out check-in for build files. For now, all pull requests can do npm run build

[aagonzales]

Not a priority but @joshblack could you check this out when you get a chance? Not sure if this has been resolved already.

[joshblack]

@aagonzales yeah for sure! Could you help fill me in on context for this? Might also be worth talking about the icon authoring flow you had mentioned earlier.

[aagonzales]

@joshblack I honestly have no clue what the context is here. This is beyond my technical knowledge. Maybe @marijohannessen or @tw15egan knows what Brian was talking about.

[aagonzales]

Or since this is in the public github maybe @hellobrian would be nice enough to give some context.

[hellobrian]

Hey! basically, this issue is about automating the build process for any SVG icons contributed to this repo. In other words, I wanted a way for Travis CI to execute the npm run build script and commit those built files to this repo automatically.

I ask contributors to either make a pull request, adding any new icons to the src directory (or I add it for them). Once merged into master, I run the build script (npm run build) to optimize the SVG file and then I make a new commit, which triggers all the npm publishing stuff via semantic-release.

I wasn't able to figure out how to do this properly when I was working on this repo, so that's the origin story of this issue. Let me know if that makes sense, and I'm happy to answer any other questions y'all may have.

[joshblack]

@hellobrian thanks for responding! 😄

Do the build artifacts need to be checked into source control, or do they just need to be published with the package itself?

[hellobrian]

@joshblack Correct, I don't think the build artifacts need to be checked into source control (everything in dist); the build artifacts just need to be published with the package itself.