This repository was archived by the owner on Apr 12, 2024. It is now read-only.
chore(travis: fix deployment condition to include tagged commits #16346
Conversation
This file contains 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
petebacondarwin
suggested changes
Nov 27, 2017
.travis.yml
Outdated
| @@ -53,10 +53,10 @@ notifications: | |||
| jobs: | |||
| include: | |||
| - stage: deploy | |||
| # Don't deploy from PRs and only from our default branches. | |||
| # Don't deploy from PRs and only from our default branches, or if tag exists | |||
There was a problem hiding this comment.
This three part sentence is a bit ambiguous. Perhaps:
Don't deploy from PRs. Only from our default branches or if tag exists.
3 tasks
Narretz
added a commit
to Narretz/angular.js
that referenced
this pull request
Dec 7, 2017
Tagged commits are not considered to belong to any branch. Closes angular#16346
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements
Other information: