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
Broken link to record-deployment
#92
Comments
Thanks. I needed to add the short link redirects to the netlify config pact-foundation/docs.pact.io@a0782fe I do this so I can put short links in the output of the CLI tools. |
Oh man, that's awesome. I'm totally going to use this in pact-js.
…On Fri, 13 Aug 2021 at 10:10, Beth Skurrie ***@***.***> wrote:
Thanks. I needed to add the short link redirects to the netlify config
***@***.***
<pact-foundation/docs.pact.io@a0782fe>
I do this so I can put short links in the output of the CLI tools.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG7HQKUVYDRTCKIOBSTOP3T4RPF5ANCNFSM5CA77ZUA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
If it's something you want to print to the screen, put a "/go/" in the link, and then in the forwarding, put in the tracking information in the redirect URL. You'll see it in the netlify file. We're using this to work out if the links we put in the output are actually effective. |
Dmitry Munda pointed out on slack that on this page:
https://docs.pact.io/pact_broker/client_cli/readme#deployments
There is this link:
https://docs.pact.io/record-deployment
which is broken and should be:
https://docs.pact.io/pact_broker/recording_deployments_and_releases/
However, when opening the readme in this repo to fix it, I saw that it's inside the autogenerated docs section. I'm not sure how that works, so I'm opening an issue instead.
The text was updated successfully, but these errors were encountered: