git-bloom-config edit groovy Repository Name: upstream Default value, leave this as upstream if you are unsure Name of the repository (used in the archive name) ['upstream']: Upstream Repository URI: Any valid URI. This variable can be templated, for example an svn url can be templated as such: "https://svn.foo.com/foo/tags/foo-:{version}" where the :{version} token will be replaced with the version for this release. ['https://google-glog.googlecode.com/files/glog-:{version}.tar.gz']: Upstream VCS Type: svn Upstream URI is a svn repository git Upstream URI is a git repository hg Upstream URI is a hg repository tar Upstream URI is a tarball ['tar']: Version: :{ask} This means that the user will be prompted for the version each release. This also means that the upstream devel will be ignored. :{auto} This means the version will be guessed from the devel branch. This means that the devel branch must be set, the devel branch must exist, and there must be a valid package.xml in the upstream devel branch. This will be the version used. It must be updated for each new upstream version. [':{ask}']: Release Tag: :{none} For svn and tar only you can set the release tag to :{none}, so that it is ignored. For svn this means no revision number is used. :{ask} This means the user will be prompted for the release tag on each release. :{version} This means that the release tag will match the :{version} tag. This can be further templated, for example: "foo-:{version}" or "v:{version}" This can describe any vcs reference. For git that means {tag, branch, hash}, for hg that means {tag, branch, hash}, for svn that means a revision number. For tar this value doubles as the sub directory (if the repository is in foo/ of the tar ball, putting foo here will cause the contents of foo/ to be imported to upstream instead of foo itself). [':{version}']: Upstream Devel Branch: Branch in upstream repository on which to search for the version. This is used only when version is set to ':{auto}'. [None]: ROS Distro: This can be any valid ROS distro, e.g. groovy, hydro ['groovy']: Patches Directory: This can be any valid relative path in the bloom branch. The contents of this folder will be overlaid onto the upstream branch after each import-upstream. Additionally, any package.xml files found in the overlay will have the :{version} string replaced with the current version being released. ['groovy']: Saving 'groovy' track.