you could get in a situation like this:
when you are at home you push some code in your project and go away for a walk, or shopping, whatever. and then you realize that you've made some little but terrible mistake in your code and if your collegues/clients/whoever will pull that update from git it will be epic fail.
imagine that you do not carry netbook/mobile/whatever-with-git-installed with yourself:
you could call or sms everyone with "DO NOT UPDATE!!" and pray that no one will update; or
you could fix that mistake fast with your mobile via web interface
By Administrator on 2012-06-26T13:51:00 (imported from GitLab project)
By Administrator on 2012-06-26T13:51:00 (imported from GitLab)
@kairn Imagine situation when you use branches, Merge Requests, code review, tests.
I've made a lot of mistakes but never pushed a broken code to stable branch.
Trying to do a quickfix often cause more bugs.
Ex: Do you trust a quickfix done by developer in hurry by Web Editor from some beer pub at 11pm :)
By Administrator on 2012-06-26T13:58:03 (imported from GitLab project)
By Administrator on 2012-06-26T13:58:03 (imported from GitLab)
I can also give you my use case: One of my trustworthy collaborator would like to be able to work on the wording of localisation files. It is no code at all with a very limited impact. Unfortunately he doesn't have the knowledge to know how to use git (fetch, rebase, commit ,pull...) and it is not his job.
So I think we have some legitimate use cases for that... but I also understand that it is not an easy feature to implement...
By Administrator on 2012-07-02T13:23:30 (imported from GitLab project)
By Administrator on 2012-07-02T13:23:30 (imported from GitLab)
@vsizov Are you working on this at the moment? I am interrested in the same thing, and figured i'll try implementing it, and maybe send of a pull request. But if you already started the work, maybe you could make your development branch/fork available (or point me too it if it is) so I could pitch in and help?
By Administrator on 2012-09-06T11:14:02 (imported from GitLab project)
By Administrator on 2012-09-06T11:14:02 (imported from GitLab)
But: Very often i am missing a function to upload and version control a new version of a file via gitlab directly, whilst maintaining a permanent link to that file.
In my projects there is some technical documentation and/or sample files that we would like to version but also share with other users that don't have git knowledge or access to it - and training them to install and use git just so they can update this file once or twice a year just isn't a viable option.
By Administrator on 2012-10-16T19:22:07 (imported from GitLab project)
By Administrator on 2012-10-16T19:22:07 (imported from GitLab)
putting together a web-based editor seems like a serious undertaking that seems to be outside the scope of something like Gitlab.
Character-encoding issues are the first thing that jumps into my mind as an issue...
The security implications of this are pretty huge to me. Cross-site request forgery (CSRF) attacks on source-code editing pages?
Just because it's something that could be done doesn't mean it's something that should be done.
Wouldn't something like this work better as a plugin for Gitlab rather than built in to the core?
If this really does get integrated into Gitlab, then I think it should be easily disabled through a configuration file for anyone who doesn't want to use it.
By Administrator on 2012-10-18T17:34:46 (imported from GitLab project)
By Administrator on 2012-10-18T17:34:46 (imported from GitLab)