-
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
Detect if new changes break existing links #793
Conversation
@MeganSteenkamp @tom-blake just been playing around with this - do you think it's necessary? I think it should only run on the production build but this is difficult as the |
a37a2dc
to
2ca57e4
Compare
It would be nice to have to get some extra confidence as long as it doesn't take too much time to make :) Perhaps running on the development build is ok? |
ee66876
to
9401ba3
Compare
9401ba3
to
6558ace
Compare
9cd8d2d
to
c85b0e8
Compare
Added a unit test which determines if any static links have been broken by iterating over the build output and comparing it to a snapshot of existing links. The test will fail if a page is removed and no redirect is added for it.
c85b0e8
to
7facfb5
Compare
7facfb5
to
7519dad
Compare
7519dad
to
2c6dc9d
Compare
Added a unit test which determines if any static links have been broken by iterating over the build output and comparing it to a snapshot of existing links. The test will fail if a page is removed and no redirect is added for it.
This allows us to migrate the legacy docs site to the new astro site with confidence. Also ensures we add the existing legacy redirects to the new astro redirects once we publish the migration
Test Plan: