It is nice at least for editing .md files to update readme/instructions/etc.
Sometimes I want to do a quick edit without having to cd directory, make sure I'm up to date, edit file, add/commit/push just for a md file in the repo
One major reason for this feature is that it's used to edit the wikis. Wikis are git projects in bitbucket so you can check them out and edit them locally, or edit them in bitbucket. For the less technical users collaborating on a project, I'd say that this feature is a big win.
It's just a start, I'm sure it wouldn't be too difficult to add these features in future for popular languages if there is demand for it. It's pretty exciting IMHO.
For the life of me I cannot comprehend why they din't use a CSS & HTML based button with native text for the "Create a free account" button. Or is it supposed to look that cheap?
This is great if you are stuck somewhere needing to change something. I really like bitbucket, about the only thing I miss on their site is a "gist" like functionality.
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).
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.
I don't believe we'll ever see developers tossing out their IDEs to edit things through the web, but this as an API this is a huge open ended solution towards automated testing.
You are doing some clojure work, you commit it, the unit tests run and fail. Clojure can tell you exactly what function failed with what data and it could commit a file for you to execute in your repl.
Using the ability to edit/create files through a webservice means the CI server running the Clojure tests could dynamically add or edit files showing the real failure over some pretty-print error message. You could check into the branch and open up user_104_error.clj and see the data that caused the problem.
When you solve the problem the CI server could automatically delete these files from the git repository, or maybe keep them around just to keep testing them.
Automated code modification into the version control system really could be interesting new ground in continuous integration and testing.
That and just last week I committed a file with the javascript url hardcoded to http://localhost/sit/js/api.js and wanted to change that back before anyone noticed.
[+] [-] planckscnst|12 years ago|reply
https://bitbucket.org/site/master/issue/2323/create-a-way-to...
[+] [-] planckscnst|12 years ago|reply
[+] [-] mixedbit|12 years ago|reply
[+] [-] rschmitty|12 years ago|reply
Sometimes I want to do a quick edit without having to cd directory, make sure I'm up to date, edit file, add/commit/push just for a md file in the repo
[+] [-] blktiger|12 years ago|reply
[+] [-] daigoba66|12 years ago|reply
As long as you have something like this in place, it doesn't matter how the change gets committed to the repository.
[+] [-] jval|12 years ago|reply
[+] [-] Alphasite_|12 years ago|reply
[+] [-] notatoad|12 years ago|reply
[+] [-] bluedino|12 years ago|reply
[+] [-] pearjuice|12 years ago|reply
[+] [-] zackbloom|12 years ago|reply
[+] [-] tonetheman|12 years ago|reply
[+] [-] hayksaakian|12 years ago|reply
[+] [-] geehsien|12 years ago|reply
[+] [-] drivebyacct2|12 years ago|reply
[+] [-] planckscnst|12 years ago|reply
[+] [-] lucisferre|12 years ago|reply
[+] [-] swombat|12 years ago|reply
[+] [-] ceejayoz|12 years ago|reply
[+] [-] defuzz|12 years ago|reply
[+] [-] mcrittenden|12 years ago|reply
[+] [-] columbo|12 years ago|reply
You are doing some clojure work, you commit it, the unit tests run and fail. Clojure can tell you exactly what function failed with what data and it could commit a file for you to execute in your repl.
Using the ability to edit/create files through a webservice means the CI server running the Clojure tests could dynamically add or edit files showing the real failure over some pretty-print error message. You could check into the branch and open up user_104_error.clj and see the data that caused the problem.
When you solve the problem the CI server could automatically delete these files from the git repository, or maybe keep them around just to keep testing them.
Automated code modification into the version control system really could be interesting new ground in continuous integration and testing.
That and just last week I committed a file with the javascript url hardcoded to http://localhost/sit/js/api.js and wanted to change that back before anyone noticed.
[+] [-] laurent123456|12 years ago|reply
[+] [-] elithrar|12 years ago|reply
GitHub has this feature, FWIW.
[+] [-] drivebyacct2|12 years ago|reply