| Issue 3031: | Set custom labels after merge | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Hi, first thanks for the great work on gerrit! We want to use gerrit to track that a feature (commit) is tested (on a test environment) or ready for deployment (on a production environment). In Version 2.9.1 though, it's not possible to change a custom label after a commit was merged. We already use custom flags in gerrit to track certain information, e.g. that a commit has passed all tests on jenkins successfully or to mark a commit manually as "ready-for-submit". As soon as all necessary flags are set, a bot merges these commits. With flags like "tested-on-test-system" we now want to track the whole life cycle of a commit. This way it would be possible to automatically cherry-pick a branch with all commits, that are marked as "tested-on-test-system", "ready-for-production" or maybe "paid-by-customer". Could you make it possible to change custom labels even after a commit was merged or is there another way to track information like this with gerrit? thx
Feb 17, 2015
Project Member
#1
edwin.ke...@gmail.com
Sep 10, 2015
Also from https://code.google.com/p/gerrit/issues/detail?id=287#c19 Topics can be changed on merged changes if the "Force Edit Topic" is set. From the ACL documentation: "Whether the topic can be edited on closed changes can be controlled by the 'Force Edit' flag. If this flag is not set the topic can only be edited on open changes." |
|
| ► Sign in to add a comment |