pages provider assumes complete control over pages repository

[adrianbroher]

The copy task of the Github pages provider currently copies the local_dir contents into the root of the checked out git repository.

However this prevents me from generating only a subdirectory of the Github pages. This can be useful to use the root for the project homepage and placing the API inside a subdirectory, maybe even separated by branch or tag name.

I would like to see a new target_dir parameter, which allows to select the target directory, where the copy task should place the files into. By default this could point to ., the root of the Github pages repository.

I would like to provide a PR if the idea is generally accepted.

[svenfuchs]

@adrianbroher i think this totally makes sense. would be happy to accept your PR!

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[adrianbroher]

Issue still persists.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues