I fail to understand why I shouldn't use my favorite editor, I'd call it a non-feature (useless, not available from the competion because it is useless).
> "not available from the competition..."
GitHub has this feature, FWIW.
Edit your code in the cloud with bitbucket
11–20 of 50 posts
Re: Edit your code in the cloud with bitbucket
#12I fail to understand why I shouldn't use my favorite editor, I'd call it a non-feature (useless, not available from the competion because it is useless).
I know that I've used GitHub's online editor a few times in situations where I see a quick typo I need to fix or want to make a one line change without the hassle of opening up the right directory, pulling the latest code, opening up an editor, etc etc.
Re: Edit your code in the cloud with bitbucket
#13Re: Edit your code in the cloud with bitbucket
#14I don't find such feature very useful. Without a way to execute code or run tests it seems too easy to break something.
Deploy to staging or test environment.
Re: Edit your code in the cloud with bitbucket
#15I fail to understand why I shouldn't use my favorite editor, I'd call it a non-feature (useless, not available from the competion because it is useless).
When I want to quickly update a readme file or comment, I find it convenient to be able to do it directly in Github (and now Bitbucket).
Re: Edit your code in the cloud with bitbucket
#16I fail to understand why I shouldn't use my favorite editor, I'd call it a non-feature (useless, not available from the competion because it is useless).
I know that I've used GitHub's online editor a few times in situations where I see a quick typo I need to fix or want to make a one line change without the hassle of opening up the right directory, pulling the latest code, opening up an editor, etc etc.
Sorry to hear that your IDE totally sucks - scnr.
It just depends on how you approach it, since I prefer to work local and upstream revisions with change notes, the main reason for revision control.
Given the featureset of github, it makes somehow sense, it just contradicts revision control to work directly in the repository.
Re: Edit your code in the cloud with bitbucket
#17I don't find such feature very useful. Without a way to execute code or run tests it seems too easy to break something.
I have a CI server which polls for the latest. It compiles and executes tests. If something fails I get notified (e-mail, etc).
As long as you have something like this in place, it doesn't matter how the change gets committed to the repository.
Re: Edit your code in the cloud with bitbucket
#18Earlier quoted context omitted.
I know that I've used GitHub's online editor a few times in situations where I see a quick typo I need to fix or want to make a one line change without the hassle of opening up the right directory, pulling the latest code, opening up an editor, etc etc.
Sorry to hear that your IDE totally sucks - scnr. It just depends on how you approach it, since I prefer to work local and upstream revisions with change notes, the main reason for revision control. Given the featureset of github, it makes somehow sense, it just contradicts revision control to work directly in the repository.
It's not always for projects that you're actively working on--I've done it a lot for projects that I have never previously touched and wouldn't otherwise go to the trouble of cloning just for a small tweak, like a random open source project with a typo somewhere.
I don't think it's at all related to the editor I use (I use vim anyway so I don't think that's the issue).
Maybe it's worth considering that others prefer different workflows than you or have different use cases?
Re: Edit your code in the cloud with bitbucket
#19Re: Edit your code in the cloud with bitbucket
#20Earlier quoted context omitted.
I know that I've used GitHub's online editor a few times in situations where I see a quick typo I need to fix or want to make a one line change without the hassle of opening up the right directory, pulling the latest code, opening up an editor, etc etc.
Sorry to hear that your IDE totally sucks - scnr. It just depends on how you approach it, since I prefer to work local and upstream revisions with change notes, the main reason for revision control. Given the featureset of github, it makes somehow sense, it just contradicts revision control to work directly in the repository.
Why are you so bothered that other people might like option to do this? Not everybody is you.