Closed guestliu closed 3 years ago
It's not recommend to do like this. Projects with fixed revisions in a manifest.xml should not been changed. If you really want to so, we may:
Is that what you want?
It's not recommend to do like this. Projects with fixed revisions in a manifest.xml should not been changed. If you really want to so, we may:
- Define two revision for project in a manifest file. One revision is a fixed revision which is used for checking out the worktree, and another revision should point to a branch which used for user to upload changes.
- The worktree will never get chance to be updated, because of the fixed revision. Any changes synced from upstream in local worktree will be treated as changes need to be uploaded to upstream.
Is that what you want?
'Latest-ok version' is a version defined by a manifest file with revisions, like the following release.xml:
Run the bash to get an error:
Expect: Run 'git repo upload' successfully when users work in a repo with latest-ok version.