| Issue 2338: | InlineEdit: Allow editing of changes in browser | |
| 4 people starred this issue and may be notified of changes. | Back to list |
Workflow: ====== * Authenticated users should be able to create, amend, discard and publish revision edits. * ACL: every authenticated user with PUSH rights can create a revision edit. * Once published revision edit is promoted to a regular patch set. * To create a revision edit, existing file(s) from a patch set must be edited or new files can be added to the patch set. * Editing take place in a popup dialog or its own screen in codemirror editor with syntax highlighting. * Revision edits are visible in the "Patch Sets" drop down as "1+": that means this revision edit was created on top of patch set 1. * Revision edits can be compared in Side by Side view, by selecting "n+" in Header Nice to have: ======== * Allow create a new change directly in browser without uploading a first patch set version from the CLI. * Integration with gitweb, cgit, gerrit-gitblit-plugin and gitiles to be able to create a new change during browsing of repositories.
Jan 30, 2014
Project Member
#1
David.Os...@gmail.com
Status:
ChangeUnderReview
Feb 11, 2014
Issue 2464 has been merged into this issue.
Sep 10, 2014
(No comment was entered for this change.)
Status:
Submitted
Labels: FixedIn-2.11
Apr 16, 2015
(No comment was entered for this change.)
Status:
Released
Jul 14, 2015
Is there a configuration setting to disable this feature? It's nice for experts but with inexperienced users it becomes too easy to create issues; for instance Change-Id mismatches or ripple effect and rebase confusion on long series.
Jul 14, 2015
> Is there a configuration setting to disable this feature? No, there is no option for this.
Jul 16, 2015
Would such a feature request be even considered?
Jul 16, 2015
Yes, I think it can be considered, but then better open a new issue as feature request for this. |
|
| ► Sign in to add a comment |