-
Notifications
You must be signed in to change notification settings - Fork 69
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
Add outbound tracking on links #1928
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Patrick Smyth <patrick.smyth@chainguard.dev>
Signed-off-by: Patrick Smyth <patrick.smyth@chainguard.dev>
Added these links to our rumble comparison pages:
|
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.
looks good, just double check /s
@@ -238,7 +238,7 @@ assume-and-explore: | |||
|
|||
Let's go over what this configuration does. | |||
|
|||
First, GitLab requires that pipelines have a shell. To this end, this configuration uses the [`cgr.dev/chainguard/wolfi-base` image](https://images.chainguard.dev/directory/image/wolfi-base/overview) since it includes the `sh` shell. | |||
First, GitLab requires that pipelines have a shell. To this end, this configuration uses the [`cgr.dev/chainguard/wolfi-base` image](https://images.chainguard.dev/directory/image/wolfi-base/overview?utm_source=cg-academy&utm_medium=website&utm_campaign=dev-enablement&utm_content=chainguard/administration/iam-organizations/identity-examples/gitlab-identity) since it includes the `sh` shell. |
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.
can you check if /s are allowed? I think they might break it and need escaped
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.
Yeah that checks out. I'll replace them with hyphens. They don't need to be machine readable anyway.
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 looked it up out of curiosity. You shouldn't use :/?#[]@!$&'()*+,;=
. Hyphen is fine.
On pause while I get a little review on the utm fields |
Description
Adding outbound tracking on links to our main CTAs, such as links to the images directory.
Reviewing
I ran a script that uses regex, it would be good to check for edge cases. I'll also do a few manual edits, I'll keep those in separate commits. The commit name will show if it's manual or automated.
Notes
I added a content field so we know what page is generating the outbound link in analytics. I've done some stuff so that it's not a useless path like "index".
References https://github.com/chainguard-dev/internal/issues/4233
cc @sheesh @ltagliaferri @SharpRake