Handle releases on Travis CI via sbt-ci-release#21
Open
alexarchambault wants to merge 3 commits into
Open
Conversation
alexarchambault
force-pushed
the
sbt-ci-release
branch
from
52f3741 to
660c0e3
Compare
alexarchambault
force-pushed
the
sbt-ci-release
branch
from
660c0e3 to
bd48eec
Compare
Member
|
Heya! I've been on paternity leave and happened to notice this. You should have sufficient permissions @alexarchambault so I'd suggest giving it a try. If not, let's figure out what permissions you're missing so that you can set it up. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Don't merge as is.
This requires the variables described here to be set up on Travis CI (by whoever has the rights to do so).
Fixes #15.