Been a while since I posted - figured I'd through this out there to hear others experiences, suggestions, etc...
I am part of a small team of 3-4 developers. We host on GH using private repos. I am the primary DM/QA/BA/etc.
Despite our limited automated tests - I still need to manually go over the application to ensure it meets (what I understand) basic requirements. Hitherto, I have requested that devs send me patch files of the changes they made. I then apply these changes to my local copy, test, valid and in some cases demo. Once satisfied with result, I apply the patch/migrations, etc to the production server.
This works OK. I typically have the patches associated to tasks in Trello - and can pull them out and keep a communication/change history very easily.
We have considered having each patch pushed to GH perhaps as a complete branch, but I have not heard a compelling enough argument to do so, as of yet. So thats what brings me here, what says you???
Regards,
Alex
Merging approved changes
Moderator: General Moderators
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
Re: Merging approved changes
What's your work flow like? Feature branches + pull requests sound like they'd work here.
- Christopher
- Site Administrator
- Posts: 13596
- Joined: Wed Aug 25, 2004 7:54 pm
- Location: New York, NY, US
Re: Merging approved changes
Hey Alex!
After reading your post, I was left wondering what the actual problem is? Is it the patches? testing the patches? or rolling out the patches?
After reading your post, I was left wondering what the actual problem is? Is it the patches? testing the patches? or rolling out the patches?
(#10850)