This is more of a question than an issue, since maybe my configuration is wrong. My build creates files that have the same name; something like this:
dist/
lib/
merge.js
merge.min.js
browser/
merge.js
merge.min.js
In my release config, with github.assets configured as a glob:
assets: ['dist/{lib,umd,browser,module}/*.js']or
or
my build in Travis CI would throw this Validation Failed / name exists error. Files were actually getting published to NPM and GitHub, but the GitHub release was flattening the paths, so only one of the merge.js and merge.min.js files was actually getting published to github.
When I configure each file individually in github.assets, like this:
assets: [{
name: 'lib.merge.js'
path: 'dist/lib/merge.js'
} ...]the error goes away and all files are correctly released in github. I guess my questions are:
- Is this intended behavior?
- Is there a way to keep the folder structure for my github release?
It would be much easier to use a glob so I wouldn't have to explicitly set each file's name and path... and that would be the behavior I would expect from a glob. Any help on how to do this is much appreciated.
This is more of a question than an issue, since maybe my configuration is wrong. My build creates files that have the same name; something like this:
In my release config, with
github.assetsconfigured as a glob:or
assets: 'dist'or
my build in Travis CI would throw this Validation Failed / name exists error. Files were actually getting published to NPM and GitHub, but the GitHub release was flattening the paths, so only one of the
merge.jsandmerge.min.jsfiles was actually getting published to github.When I configure each file individually in
github.assets, like this:the error goes away and all files are correctly released in github. I guess my questions are:
It would be much easier to use a glob so I wouldn't have to explicitly set each file's name and path... and that would be the behavior I would expect from a glob. Any help on how to do this is much appreciated.