Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

gh-pages (document release branch) should be automatically populated #1721

Closed
ashahi1 opened this issue Aug 8, 2017 · 3 comments
Closed

Comments

@ashahi1
Copy link
Contributor

ashahi1 commented Aug 8, 2017

Currently, any changes to [vmware]/docs has to be manually copied to gh-pages. The process should be automated - any changes to [vmware]/docs should be promoted to gh-pages automatically

https://github.com/vmware/docker-volume-vsphere/blob/master/CONTRIBUTING.md#documentation-pr

@ashahi1 ashahi1 added the P1 label Aug 8, 2017
@ashahi1 ashahi1 self-assigned this Aug 8, 2017
@pdhamdhere
Copy link
Contributor

Changes should be promoted from master to gh-pages every time we cut release. And this is P0 and must be fixed before next release.

@shuklanirdesh82
Copy link
Contributor

shuklanirdesh82 commented Aug 25, 2017

PR #1798 is bringing doc changes from vmware:master to vmware:gh-pages automatically.

Next step:

targeted work for Mufasa sprint is done and moving this issue to next sprint to have automated job.

@ashahi1
Copy link
Contributor Author

ashahi1 commented Aug 30, 2017

Filed a separate issue for creating a cron job - #1854

@ashahi1 ashahi1 closed this as completed Aug 30, 2017
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

4 participants