Add the ability to edit and delete repositories

Deleting a repository under this scheme will also delete all branches associated with that repository. Editing a repository name updates repo_name on the branches.

[Collin Winter, 2009-04-11 01:05:14]

Andi, could you take a look at this patch when you get a chance?

[Collin Winter, 2009-04-14 21:31:09]

On 2009/04/11 01:05:14, Collin Winter wrote:
> Andi, could you take a look at this patch when you get a chance?

Updated the patch to include r408 (from issue 40053).

[Andi Albrecht, 2009-04-14 21:49:36]

http://codereview.appspot.com/40054/diff/20/21
File codereview/views.py (right):

http://codereview.appspot.com/40054/diff/20/21#newcode2366
Line 2366: @login_required
What about adding a repo_owner_required decorator, similiar to the
issue_owner_required decorator?

http://codereview.appspot.com/40054/diff/20/21#newcode2393
Line 2393: branch.put()
I think it's better to use google.appengine.ext.db.put() here which takes a list
of objects to save, instead of saving each instance separately.

In addition I would add the repo to that list and add commit=False to the
form.save call.

http://codereview.appspot.com/40054/diff/20/21#newcode2405
Line 2405: return HttpResponseForbidden('Invalid request method: %s' %
request.method)
There's a post_required decorator defined in views.py

http://codereview.appspot.com/40054/diff/20/21#newcode2410
Line 2410: repo.delete()
google.appengine.ext.db.delete() with a list of objects to delete like in
views.delete() does the same in a single transaction.

http://codereview.appspot.com/40054/diff/20/24
File templates/repo_edit.html (right):

http://codereview.appspot.com/40054/diff/20/24#newcode17
Line 17: <tr><td><input type="submit" value="Delete This Repository"></td></tr>
The "Delete Issue" button on the edit issue page has a nice and convincing
warning ("There's no undo!"). Maybe we should at a similar notice here too...
;-)