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.

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

Setup sync job for wiki #5671

Closed
Tyriar opened this issue Apr 22, 2016 · 10 comments
Closed

Setup sync job for wiki #5671

Tyriar opened this issue Apr 22, 2016 · 10 comments
Assignees
Labels
debt Code quality issues feature-request Request for new features or functionality
Milestone

Comments

@Tyriar
Copy link
Member

Tyriar commented Apr 22, 2016

https://github.com/Microsoft/vscode.wiki.git needs to sync back and forth with https://github.com/Microsoft/vscode-wiki.git so PRs on vscode-wiki are pulled in to vscide.wiki and vise versa.

See #5669 and #5670

@Tyriar Tyriar self-assigned this Apr 22, 2016
@Tyriar Tyriar added this to the May 2016 milestone Apr 22, 2016
@egamma egamma mentioned this issue May 6, 2016
87 tasks
@gep13
Copy link
Contributor

gep13 commented May 11, 2016

@Tyriar I started to do this work with a couple projects, but decided that the overhead wasn't worth it. Instead, all documentation for my projects now live in the same repo as the source code, and I use https://readthedocs.org/ to display them. That way, documentation PR's are exactly the same as code PR's.

Will be interesting to see what you put together though.

@Tyriar
Copy link
Member Author

Tyriar commented May 11, 2016

@gep13 that's what we just transitioned to, however we decided that we'd prefer to keep the doc PRs/commits away from the product changes.

This is only an issue because GitHub wiki's cannot be forked unfortunately 😦

@gep13
Copy link
Contributor

gep13 commented May 11, 2016

@Tyriar said...
however we decided that we'd prefer to keep the doc PRs/commits away from the product changes.

I can understand the need for that, we just like to keep everything in one place though :)

@Tyriar Tyriar added debt Code quality issues feature-request Request for new features or functionality labels May 19, 2016
@Tyriar
Copy link
Member Author

Tyriar commented May 19, 2016

This is ready to go from a community perspective, we just need to sync the changes manually until the sync job is setup.

@Tyriar Tyriar modified the milestones: June 2016, May 2016 May 23, 2016
@Tyriar Tyriar modified the milestones: July 2016, June 2016 Jun 25, 2016
@Tyriar
Copy link
Member Author

Tyriar commented Jul 7, 2016

I setup a job on VSTS, building daily. Leaving this open for a while to confirm it works.

@gep13
Copy link
Contributor

gep13 commented Jul 11, 2016

@Tyriar do you have any details of the VSTS job that you are running? Thanks!

@Tyriar
Copy link
Member Author

Tyriar commented Jul 11, 2016

@gep13 it's closed unfortunately but it just runs a few git commands. Here's what it does:

git clone https://github.com/Microsoft/vscode-wiki.git
cd vscode-wiki
git remote remove upstream # continue if this line fails
git remote add upstream https://github.com/Microsoft/vscode.wiki.git
git fetch upstream
git merge upstream/master
git push origin HEAD:master
git push upstream HEAD:master

@gep13
Copy link
Contributor

gep13 commented Jul 12, 2016

@Tyriar thank you for the information!

@Tyriar
Copy link
Member Author

Tyriar commented Jul 12, 2016

The job failed due to lacking git username/email, after adding that the job synced vscode-wiki and vscode.wiki just fine, merging in microsoft/vscode-wiki#4 to vscode.wiki https://github.com/Microsoft/vscode/wiki/How-to-Contribute#pull-requests 🎉

@Tyriar Tyriar closed this as completed Jul 12, 2016
@ferventcoder
Copy link

This is interesting. Similar to what we do with choco. Typically however we'd do a rebase instead of a merge.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Code quality issues feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants