Skip to content
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

What to do with .travis.yml when there's already a .travis.yml in the upstream project #46

Closed
juxor opened this issue Aug 13, 2017 · 0 comments
Closed

What to do with .travis.yml when there's already a .travis.yml in the upstream project #46

juxor opened this issue Aug 13, 2017 · 0 comments

Comments

@juxor
Copy link

juxor commented Aug 13, 2017 •
edited

When importing upstream with gbp the upstream code will be placed in the rood directory, so if the project already have a .travis.yml and following the instructions in [0], it'll have to be replaced with with the one for debian.
Which would be a recommended way to manage this?.
Thanks.

[0] http://travis.debian.net/#quick-setup
@lamby lamby closed this as completed in 2102807 Aug 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@juxor