-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle multiple developers? #11
Comments
Hi @heteneik , Let me know if that makes sense . |
Hi @vrosu Up to a certain point it does make sense yes, but if multiple people working on multiple projects for example, the git configuration is visible to everybody. Independently what they are working on. Maybe I am missing a point here, but so far what I've seen is that I configured the git extension with my personal stash account the following happens:
On the other hand working on a single project with 2+ designer, even if it does not always efficient it is very much possible and in our case from CI/CD perspective it would be nice to see who did what exactly when they commit their changes. The only workaround I'm having right now is that we are doing a single weekly commit with the team that is tied to one user and we are reviewing the the changes at once instead of reviewing pull requests. EDIT: Are you actually talking about duplicating the entire extension for each user? |
Do you have any recommendation as to how to duplicate the extension? Without going and individually duplicate the entities? |
I was not referring to duplicating the extension, but to create a GitBackup Thing per developer. I just remembered, not sure if you've looked at this, but regardless of the user who is used to access the repository, each user can setup his own committer name and email when pushing a commit to a branch - different to the user setup in the GitBackup configuration. In this way you can have a single GitBackup thing. In this case, the user should be considered a technical user of sorts. The commits will in this case show up with who did them. |
Hi @heteneik . Did you have a chance to look at the message above? If so, can you share your feedback for the community? Thanks! |
Hello @vrosu, I'm still evaluating the possibilities. What I can tell is that I have a solid process for a single developer / single environment to propagate changes from DEV to PROD, but I am still unsure how safe / usable this is going to be with multiple users using the DEV system. In my opinion if the dashboard / workspace would be tied to a user, that'd be the best, but I understand the complexity that would bring for you to develop it. I'll come back later to finish my thoughts :) |
Hi @vrosu,
It's more like a question, but do you have any plans to somehow handle multiple developer using a single instance?
The text was updated successfully, but these errors were encountered: