We had a case today where a user accidentally created a branch for an RFD number which is already on the default branch in the published state. This should be a no-op and we should be ignoring the branch since it is not authoritative. In practice a new revision was created with the contents of the new branch.
We had a case today where a user accidentally created a branch for an RFD number which is already on the default branch in the published state. This should be a no-op and we should be ignoring the branch since it is not authoritative. In practice a new revision was created with the contents of the new branch.