Refactor terminology of ref and branch in scripts
From man ostree
:
TERMINOLOGY
The following terms are commonly used throughout the man pages. Terms in upper case letters are literals used in
command line arguments.
BRANCH
Branch name. Part of a REF.
COMMIT
A SHA256 hash of a commit object.
REF
A reference to a particular commit. References are text files stored in refs/ that name (refer to) a particular
commit. A reference can only be the branch name part, in which case a local reference is used (e.g.
mybranch/stable). If a remote branch is referred to, the remote name followed by a colon and the branch name
needs to be used (e.g. myremote:mybranch/stable).
REV, REFSPEC
A specific revision, a commit. This can be anything which can be resolved to a commit, e.g. a REF or a COMMIT.
Thus branch is always a ref, but ref is not always a branch, examples:
fedora/stable/x86_64/iot
-- it's a branch and it's a ref
fedora-iot:fedora/stable/x86_64/iot
-- it's NOT a branch but it's a ref
In cases where branch and remote are supposed to be handled by different vars/opts it's suggested to use appropriate terminology.