Skip to content
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

Merged
merged 2 commits into from
Jan 10, 2022
Merged

setup CI #8

merged 2 commits into from
Jan 10, 2022

Conversation

iwysiu
Copy link
Contributor

@iwysiu iwysiu commented Jan 7, 2022

Part of #6

@iwysiu iwysiu requested review from a team, sarahzinger and yaelleC and removed request for a team January 10, 2022 15:37
Copy link
Member

@sarahzinger sarahzinger left a 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
Copy link
Member

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?

Copy link
Contributor Author

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.

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
Copy link
Member

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?

Copy link
Contributor Author

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.

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.

@iwysiu iwysiu merged commit 6780d43 into main Jan 10, 2022
@iwysiu iwysiu deleted the add-ci branch January 10, 2022 16:53
Copy link

@andresmgot andresmgot left a 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

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

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.

@andresmgot
Copy link

my review arrived a minute late 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants