-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip publish for whitelisted files #3
Comments
Could we automatically derive the whitelist as files that are not in any |
Yes, we could, good point. We should also detect changes in:
I think I'm not missing anything, but haven't devoted it too much thinking. |
By the way, for some of the files, you can already do this with Drone by adding |
I'm adding this for an spree. Hope this will get solved in Lambda World at the end of October. |
How about adding Hacktoberfest label? 🍻 😉 |
We call them sprees because that's the official name https://github.com/scalacenter/sprees. But we can add another label for the awesome |
Cool! I didn't know about scalacenter/sprees (I thought it's just another word for "hackaton"). 👕 More free t-shirts to the god of t-shirts! 😆 |
Yeah, and hope we see each other in a spree soon so that I can you your well-deseved t-shirt! We usually organize them in popular Scala conferences. Next up is Lambda World, in Cadiz, at the end of the month. |
Haha 😅 that's a fortunate coincidence! I'm coming to Lambda World (I live in Granada, so it's relatively close). |
Well, that's awesome 😄! We'll go for a beer. You can also join us at the spree, we're looking for maintainers that would propose tickets in their projects. Your sbt plugins would be a great fit for the spree if you have low-hanging fruits like this one 🎉. |
Cool! 🍻
Sounds great 👍 I will think about it and add something to scalacenter/sprees. |
There are files in a repository, like docs, that should not affect the compilation of the project and therefore publish a new artifact (the artifact will be the same as the one previously released).
I would like
sbt-release-early
to allow me to define the whitelisted files in my build in the following way:When I commit this setting implementation, the
releaseEarly
would not trigger the publish task if only those files have been modified. If there's a change in any other file, it will publish an artifact as expected.The implementation of this feature cannot assume that the previous commit has been released, and therefore we need to get the modified files since the last published commit (contrary to the last commit, i.e. HEAD~1).
The text was updated successfully, but these errors were encountered: