tree 7b3e3bfd5922614fa9d941890163c5eb0c3c74c8
parent 1f37e09c2383a9fa6cc2970e749b1195dd08c663
author Edwin Kempin <ekempin@google.com> 1642695331 +0100
committer Edwin Kempin <ekempin@google.com> 1642761249 +0100

Fix submit rule for changes for which the target branch doesn't exist

There are 2 possibilities to have changes where the target branch
doesn't exist:

1. An initial commit is pushed for review to the not yet created master
   branch (that's a hard-coded special case where Gerrit allows
   uploading a change for an unborn branch).

2. A change is created for an existing branch and the branch gets
   deleted afterwards.

At the moment the code owner submit rule returns not ready in this case.

Since the target branch of the change doesn't exist it cannot contain
OWNERS files that define code owners. However it is possible that there
are default code owners (defined in refs/meta/config), global code
owners (defined in code-owners.config) or fallback code owners
(configured via code-owners.config) that could approve the change. In
addition there can be a code owner override that code-owner-approves the
change.

Now, if the target branch doesn't exist, CodeOwnerApprovalCheck skips
checking code owners from OWNERS files in the target branch, but still
checks default, global and fallback code owners, as well as overrides.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Idfcec9c0dc1601ae4cbd2185203e658a6a65b713