![]() ![]() Adding Custom HTML WidgetsĪdding custom HTML (or code sandbox) to a tag should be migrated from Mattertag.injectHTML to Tag.registerSandbox and Tag.attach. Tags now support multiple media (or attachments) per tag. Providing media in Mattertag.add or Mattertag.editBillboard should be migrated to use Tag.registerAttachment and Tag.attach. Eventually, this will also be the case for Pointer.editTexture. Instead, Asset.registerTexture should be used. The Tag namespace does not have a registerIcon function like the Mattertag namespace does. We have moved to a unified texture registry for icons and other visuals. Mattertag.registerIcon should be migrated from Mattertag.registerIcon to Asset.registerTexture. A brief summary of the major changes Existing Functionality However, any future Tag capabilities will be added to the Tag namespace. After the full release, the Mattertag namespace will be considered deprecated, but still functional. The Mattertag namespace should continue to work whether or not the application is using Tags 2.0. Rather than shoehorning a new interface on top of an existing namespace, Tags 2.0 (Tags) seek to provide the foundation for more powerful tag-based capabilities in the future. However, the Mattertag interface and architecture doesn’t directly support future extended capabilities, such as hosted content. Traditional Mattertags allow for the viewing of embedded content and information about particular locations within a Matterport space. Some are now more robust and require more than a single step to use. Most operations that are available in the Mattertag namespace have an equivalent operation in the Tag namespace. Note it's redundant to find the commit hash for HEAD.Tags (2.0), is the successor to Mattertags. if `git describe -contains HEAD 2&>1 > /dev/null` then Note using 2> /dev/null to suppress error output.īut it's safer to instead completely ignore the output and check the exit value. NEEDS_TAG=`git describe -contains HEAD 2> /dev/null` You can use -n to look for a non-empty string and flip the logic. Your program will always tag because -z looks for a null string, it will still fire on "". $ git tag -points-at HEADĪs will git log -decorate $ git log -decorateĬommit 8ce1cfebecda68ba42226d0e6cd5dbebba76ae0b (HEAD -> master, tag: foo, tag: bar) Git tag -points-at HEAD will show all tags that point at the current commit. $ git describe -abbrev=0 -tagsįatal: No names found, cannot describe anything. Multiple tags can point to a single commit, but git describe -abbrev=0 -tags will only show one. You can see I've fetched the latest tags and it shows v0.0.8, but still shows v0.0.7 as the current tag of the repository. #only tag if no tag already (would be better if the git describe command above could have a silent option)Įcho "Tagged with $NEW_TAG (Ignoring fatal:cannot describe - this means commit is untagged) " NEEDS_TAG=`git describe -contains $GIT_COMMIT` ![]() #get current hash and see if it already has a tag Git commit -allow-empty -m "Updating $VERSION to $NEW_TAG" #get number parts and increase last one by 1 This is the source code of the script: $ cat archive/tag_git_repo.sh Tagged with v0.0.8 (Ignoring fatal:cannot describe - this means commit is untagged) It's supposed to update from the latest tag v0.0.8 to v0.0.7./archive/tag_git_repo.sh Git failing to update tag with fatal: tag 'v0.0.8' already exists ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |