-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup CI #8
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to work! 🎉
|
||
--- | ||
kind: signature | ||
hmac: 37437b11206f698eec8f7642f882760922190d6acd31117902b21e3b26327f6a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just curious what does this do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes have to be signed for drone to run the drone file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the signature is obtained from drone.grafana.net so only authenticated people there can modify this file
@@ -1,4 +1,5 @@ | |||
//+build mage | |||
//go:build mage | |||
// +build mage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what do these comments do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think mage or vs code automatically changed those for me, but its the mage build tag so it knows what files to parse.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are go build tags (the first one is added automatically by the formatter)
A magefile, instead of having a magic name (like Makefile), uses the go build tag //+build mage to indicate that mage should read it. Other than that, there’s nothing special about magefiles and you can name them whatever you like.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
|
||
--- | ||
kind: signature | ||
hmac: 37437b11206f698eec8f7642f882760922190d6acd31117902b21e3b26327f6a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the signature is obtained from drone.grafana.net so only authenticated people there can modify this file
@@ -1,4 +1,5 @@ | |||
//+build mage | |||
//go:build mage | |||
// +build mage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are go build tags (the first one is added automatically by the formatter)
A magefile, instead of having a magic name (like Makefile), uses the go build tag //+build mage to indicate that mage should read it. Other than that, there’s nothing special about magefiles and you can name them whatever you like.
my review arrived a minute late 😆 |
Part of #6