MichaelVoigt's Forum Posts

  • 3 posts

  • You can work more collaboratively by using a project that is saved as a folder. The folder is full of the project files. So you can merge just the ones you changed. You don't have to merge a massive single project file.

    My team of 3 has been working smoothly for 3 days. Just sharing what file with you team and ensuring they all have pushed that file to GIT is all you need to do. It's like checking-out files and virtually locking them. Using human communication.

    I'm looking if Git has a file check-out or lock feature for a branch. I think that is how the other branching program PerForce does things.

  • Thanks, Ashley! First, I'll apologize for being a designer on a team of three designers that don't have access to engineers. We are rapidly building a game for a non-technical client. We all work in the same timezone and need to collaborate during our business hours. The game requires all three of us to be able to add images, sounds, and other files throughout the day.

    I read the tutorial that you sent, which is great. But I didn't see an easy solution for us.

    To not block progress, here is what I've proposed for us to keep working. BTW, our project is a folder based project, and we have the proper gitIgnore, and our UID numbering is 'Random'.

    1. Each day, one person will be the designated person who can add files to the project. Only they can push changes that involve project.3proj. They will push those into the Main branch.

    2. For the rest of that day, the rest of the team can make changes that don't change project.3proj. They periodically check gitDesktop to verify they are fine. And we communicate all day to avoid conflicts.

    3. The next day, we push our changes to our Main branch and communicate and fix conflicts.

    We are open to any feedback. We tested this process this morning, and it worked.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Is this a fair summary - for collaborating with Construct 3 today this is recommended as the solution:

    1. One team member has to add all assets to the project. And they push that upward to a branch. This team member is in charge of all asset management.

    2. Other team members pull from that branch and add interactivity. But do not add new assets. This ensures when they submit changes that the project won't break.

    Is that basically the best and easy workflow?

  • 3 posts