github links obsolete about prometheus-am-executor HOT 3 CLOSED

We haven't built this in a while. Can you patch, test, and submit a PR?

from prometheus-am-executor.

Going to take a look at this as part of setting up travis-ci support.

from prometheus-am-executor.

The package path used for import statements in go code tells go where the package definition for template or prometheus packages are; It's not meant to contain vcs-specific details like versioning or branch; That's handled separately in go.mod or vendoring. So, the path you use in import statements matches the path you'd see on your filesystem in a git clone of a repository, but may not match what you'd see in your browser when navigating a github repository.

If you wanted to target the master branch specifically, instead of a tag or pseudo-version, you would keep the path name the same as before, and issue a command like

go get -v github.com/prometheus/alertmanager/template@master

This golang blog post has more details on package names/paths :).

from prometheus-am-executor.