git tag - How can I create a git alias to delete a tag remotely? -


i'm having trouble creating git alias delete tag remotely.

i have following in .gitconfig:

[alias]   deltag = push origin :refs/tags/$1

running deltag alias after deleting tag locally (with git tag -d testtag) results in error:

$ git deltag testtag error: src refspec testtag not match any. error: failed push refs 'ssh://........'

attempting run alias before deleting locally results in instead:

$ git deltag testtag remote: warning: deleting non-existent ref. ssh://........ - [deleted]         $1

what correct syntax use alias?

i solved hunting around on stackoverflow , putting other answers together.

there may other solutions too, turning alias shell command passes tag argument through:

[alias]   deltag = !sh -c 'git push origin :refs/tags/$1' -

or better, combining both local , remote delete 1 alias:

[alias]   deltag = !sh -c 'git tag -d $1 && git push origin :refs/tags/$1' -

the output:

$ git deltag testtag deleted tag 'testtag' (was be73a23) ssh://.......  - [deleted]         testtag

-

Popular posts from this blog

Apache NiFi ExecuteScript: Groovy script to replace Json values via a mapping file -

i working apache nifi 0.5.1 on groovy script replace incoming json values ones contained in mapping file. mapping file looks (it simple .txt): header1;header2;header3 a;some text;a2 i have started following: import groovy.json.jsonbuilder import groovy.json.jsonslurper import java.nio.charset.standardcharsets def flowfile = session.get(); if (flowfile == null) { return; } flowfile = session.write(flowfile, { inputstream, outputstream -> def content = """ { "field1": "a" "field2": "a", "field3": "a" }""" def slurped = new jsonslurper().parsetext(content) def builder = new jsonbuilder(slurped) builder.content.field1 = "a" builder.content.field2 = "some text" builder.content.field3 = "a2" outputstream.write(builder.toprettystring().ge...
Read more

node.js - How do I prevent MongoDB replica set from querying the primary? -

read-operations-only: is there way have mongodb replica set, make mongodb instance on box connected to, mongodb gets queried? i have 3 ec2 instances behind aws load balancer. on each ec2 instance runs mongodb, part of replica set. i have express endpoints on nodejs , connect replica set follows mongodb.mongoclient.connect('mongodb://1.1.1.1,2.2.2.2,3.3.3.3.', function (err, db) { if (err) { complete('{}'); } else { i distribute load of queries evenly across 3 instances of mongodb replica set instead of default having queries routed ec2 instance primary mongodb defined, because destroys point of load balancer (which balance load of queries across 3 instances evenly). my understanding when connecting mongodb replica set, primary instance selected unless primary instance down, , therefore purpose of every secondary instance serve backup. in example people call hot,cold,cold. because there 2...
Read more