Workflow for multiple devs working in one project

The scenario is that in my team, we want to have a good developer workflow for Apps scripts project. Then we decided to use clasp with Typescript on it.

When we run clasp push, the .ts files get transformed in .gs files in scripts.google.com.

If there are multiple devs working on one project and do push simultaneously, I’m pretty sure the first push will be overwritten by the second push and we will lose the progress.

Can you recommend a good developer workflow in this type of scenario?

[Nu11u5]

GAS should be treated only as a deployment target.

If individual developers need to test code they can configure their own GAS project file and push to that. If the GAS project is linked to a GCP project, all “copies” can be linked to the same GCP project if needed.

[schulzj01]

Hello Everyone, I have the same issue, unfortunate you can have different devs for a same project, but each push request does overwrite in all files in apps script. It would be better we have the possibility to do pull request for separate, I mean for spared files without overwrite all project in app script.

We have a multi-developer application and here’s how we handle this.

1. Set up each developer with their own GAS project.
2. Each developer pulls from the git repo.
3. Each developer creates a .clasp.json file which is different for each developer, and adds .clasp.json to their .gitignore file.
4. Developers would test off their separate GAS project, finalize changes, and then push back to the git repo.
5. Once you’re ready to deploy, create a separate GAS project, push your repo code, and create the deployment from that.
6. Subsequent deployments run off the project created in the previous step.