search

xforty / xforty-drupal

xforty technologies base drupal distro
Other
5 stars 3 forks source link

Document how to dev and test without having to commit and push changes to github #5

Open dkingofpa opened 12 years ago

dkingofpa commented 12 years ago

In the past, we've just committed changes to the master branch and then tested as we built a new site. As a result, there have been a large number of tags created for versions that ultimately were broken as we tested.

I believe we can mostly avoid these "throw-away" tags by making our changes in a feature branch. We can test our changes by referencing that feature branch in our distro.make. Once we've done some testing, then we can merge that branch back to master. This won't prevent all of these throw-away tags, but it should cut down on the number of them significantly.

dkingofpa commented 11 years ago

I've also been using vagrant-drupal and some symlinks to develop and test locally before committing the changes.

pearcec commented 11 years ago

Is this documented?

dkingofpa commented 11 years ago

No, it's not. Just wanted to mention it for whenever we do get around to documenting the process.

dkingofpa commented 11 years ago

Since this project doesn't leverage git-flow, we don't have master and develop branches. As a result, we'd probably have to manually create and manage the feature branches. Another option may be forking to a personal github account and then doing a pull request.

pearcec commented 11 years ago

I am find with personal and pulls for now. It would nice to experience that.