You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 19, 2022. It is now read-only.
Hi, thanks for this great software. Our use case is not for coding, but storing configuration files for the apps we run. We have teams of application admins (and DBAs) who do not know how to use git in the traditional sense. All I want them to be able to do is browse the git repo for their config file, edit the file using the browser editor, and then be forced to add a comment on what they changed and commit it. This way we have version control and can track who did what to the config files.
I'm thinking in the user control panel have a check box to indicate this user is git oblivious and then the only thing they can do with regards to git is edit files in the browser editor and then be forced to enter a comment and then commit. Any other git options would need to be hidden from them. I thought maybe once a file is saved it triggers the Commit dialog so they are forced to add a comment and then commit if they save a file. I know something gets triggered on save because it shows a visual cue in the left panel when the git repo is changed.
I did find out by editing the templates/overview.html file I can hide the git options except for Commit...but this hides it for everyone. I'm not a programmer so this is just me stabbing at it.
Any thoughts on that? Thanks!
The text was updated successfully, but these errors were encountered:
Sry for my late response. This would be theoretical possible but it is not the normal use case of git. This would require some hughe changes for which I don't have the time. I let this issue open if someone wants to help.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, thanks for this great software. Our use case is not for coding, but storing configuration files for the apps we run. We have teams of application admins (and DBAs) who do not know how to use git in the traditional sense. All I want them to be able to do is browse the git repo for their config file, edit the file using the browser editor, and then be forced to add a comment on what they changed and commit it. This way we have version control and can track who did what to the config files.
I'm thinking in the user control panel have a check box to indicate this user is git oblivious and then the only thing they can do with regards to git is edit files in the browser editor and then be forced to enter a comment and then commit. Any other git options would need to be hidden from them. I thought maybe once a file is saved it triggers the Commit dialog so they are forced to add a comment and then commit if they save a file. I know something gets triggered on save because it shows a visual cue in the left panel when the git repo is changed.
I did find out by editing the templates/overview.html file I can hide the git options except for Commit...but this hides it for everyone. I'm not a programmer so this is just me stabbing at it.
Any thoughts on that? Thanks!
The text was updated successfully, but these errors were encountered: