Auto deploy and Issue/PR templates #44
Merged
Conversation
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
|
@nicolasblanco merging in and trying it with release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This PR is not feature-related, but instead adds the following to the repo:
Additional Notes
Auto deployment key has been safely encrypted and deploy will trigger only when a new tag is pushed. This will automatically happen every time we create a new release here on GitHub.
Travis will also proceed with the release only if the tests are passing for Ruby 2.3.1 and Rails 4.2.
In case we added a more recent version of Ruby/Rails to the travis matrix, this condition should be updated as well.
@nicolasblanco please review this one and let me know if you have anything against it 😄