Skip to content

Add after_success and branch examples (#1) #597

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Jun 9, 2016
Merged

Add after_success and branch examples (#1) #597

merged 2 commits into from
Jun 9, 2016

Conversation

gravyboat
Copy link
Contributor

  • Add after_success and branch examples
  • Remove a comment

@gravyboat
Add after_success and branch examples (#1)
70e8e76 
* Add after_success and branch examples

* Remove a comment
@gravyboat
Copy link
Contributor Author

gravyboat commented May 31, 2016 •
edited
Loading

This resolves travis-ci/travis-ci#5065.

Edit: I realized there are no docs dedicated to after_success so hopefully this is the right place, if there was a dedicated page I would have put it there.

@plaindocs plaindocs self-assigned this Jun 2, 2016
@gravyboat
Copy link
Contributor Author

@plaindocs Is there anything missing from this that's keeping it from being merged? If so please let me know and I'll fix it up.

plaindocs
plaindocs reviewed Jun 7, 2016
View reviewed changes
user/docker.md

Using `after_success` it is also possible to push an image to a registry based
on the branch:

This comment was marked as spam.

Sign in to view

@plaindocs
Copy link
Contributor

Comments above, sorry for the delay.

@gravyboat
Copy link
Contributor Author

No worries, I'll update this as soon as I get a chance.

@gravyboat
Copy link
Contributor Author

Okay this is all fixed up, thanks for the feedback.

@plaindocs plaindocs merged commit ceab69e into travis-ci:gh-pages Jun 9, 2016
@plaindocs
Copy link
Contributor

Thanks! :-)

@Silex
Copy link

Silex commented Feb 22, 2018 •
edited
Loading

This fails for pull requests. You need to ensure it's not the PR pushing otherwise someone can push whatever he wants.

@plaindocs plaindocs mentioned this pull request Feb 22, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@plaindocs plaindocs

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@gravyboat @plaindocs @Silex