Managing collaboration challenges when multiple team members work on the same prompt file.

Currently, in our project, multiple team members are working on enhancing different parts of the same prompt file. This is sometimes causing inconvenience, as changes made by one person tend to affect others’ work.
Have any of you faced a similar situation? If so, could you please share any suggestions on how to handle this more effectively?

The way I manage this is by using tags. Imagine there is a prompt named xyz.

Whenever a developer makes changes to the prompt, they tag it with their unique identifier, for example, mmk. In the end, there may be multiple final versions of the prompt, each created by a different developer and tagged accordingly e.g xyz:mmk, xyz:bt.

Once all the changes are complete, a single person consolidates them into one unified prompt and assigns it a tag such as staging, and later, a tag like prod. Therefore final prompt will be ‘xyz:prod‘

The tagging of commits also makes sure that every developer can only pull their own prompt.

Doc Reference: Manage prompts - Docs by LangChain (How tags work)
Manage prompts programmatically - Docs by LangChain (Pulling Prompt)

1 Like

@Bitcot_Thamarai can you mark the last answer as the solution if possible.