Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript

Adam Duffield
Adam Duffield
30,494 Points
Posted by Adam Duffield
Adam Duffield
30,494 Points

Anybody familiar on working with Git and Gulp in a Team? Having major problems syncing files with different hashes

Hi All!

At my current workplace we are working with gulp to build all our files from a src folder to the root directory of the project, all my assets files have hashes and we set harsh caching rules so that everytime we make a change the site updates with the new hashed file and deletes the old one.

Trying to work with Git and Gulp in a team with this build seems a nightmare. We just want to be able to work from our src file and push that to our dev branch and have gulp build from the src to the root directory and then push the root to the master branch but we're running into many issues.

It's not so much a GIT problem, we understand git but the way we build our files seems to clash with the idea of working on a project with other team members.

Anyone out there had a similar problem or similar build?

Many thanks!

1 Answer

Kevin Korte
Kevin Korte
28,149 Points
Kevin Korte
Kevin Korte
28,149 Points

Could you guys just check in your source files, and that let each dev's computer recompile the root code with whatever hash that local computer has?

All you guys really need are the changes a dev made to the source files, right? Than you could pull those changes and let gulp compile the root code on your local machine.

And than only when you're ready for a production release, manually push the root to the master branch from one users computer.