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

Eliminate wordpress-trunk from default provisioning #921

Closed
jeremyfelt opened this issue Jun 14, 2016 · 3 comments
Closed

Eliminate wordpress-trunk from default provisioning #921

jeremyfelt opened this issue Jun 14, 2016 · 3 comments
Assignees
@jeremyfelt
Labels
for:documentation type:enhancement
Milestone
1.4.0

Comments

@jeremyfelt
Copy link
Member

In #113, we made the switch from core.svn to develop.svn and I left wordpress-trunk as it was with the worry that we would break an existing configuration.

I think we can stop checking out core.svn during provisioning. I don't think it will cause any conflicts. We'll just need to communicate that everyone is on their own to svn up when they want updates...

...which is probably how we should have done the SVN stuff to begin with. :)
@jeremyfelt jeremyfelt mentioned this issue Jun 14, 2016
Closed
@jeremyfelt jeremyfelt changed the title Elimintate wordpress-trunk from default provisioning Eliminate wordpress-trunk from default provisioning Aug 2, 2016
@jeremyfelt jeremyfelt added this to the 1.4.0 milestone Aug 2, 2016
jeremyfelt added a commit that referenced this issue Aug 16, 2016
@jeremyfelt
Remove WordPress trunk from default provisioning
faf16ca 
This has been around since the beginning of VVV, when the develop
repos had not yet been created. There's not much sense in providing
both the legacy trunk repo and the modern develop repo.

We'll still want to document the best way to continue using the
wordpress-trunk directory if it exists in your VVV instance.

See #921.
@jeremyfelt jeremyfelt mentioned this issue Aug 16, 2016
Merged
@jeremyfelt
Copy link
Member Author

#959 removes trunk from provisioning. We should probably have documentation for how to add a vvv-init script that keeps it going if it is part of your daily workflow.

@jeremyfelt jeremyfelt self-assigned this Aug 20, 2016
@jeremyfelt
Copy link
Member Author

Fixed in #959.

@lock
Copy link

lock bot commented Feb 22, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremyfelt jeremyfelt

Labels
for:documentation type:enhancement
Projects
None yet
Milestone
1.4.0
Development

No branches or pull requests
1 participant
@jeremyfelt