Testing out PR with build #656
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for a11ycanada ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
…d deploy - Merged `update-analytics` and `deploy` jobs into a single consolidated job - Updated workflow to run on schedule, manual dispatch, or after a PR is merged to `main` - Simplified deployment logic to ensure analytics updates and deployment occur together post-merge - Adjusted conditions to prevent deployment from running on every push, relying on Netlify for PR previews
plansmash-test
force-pushed
the
fix-build
branch
from
f670693
to
c10e0df
Compare
|
PR was just a test from a non-maintainer account |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's see if this works. I think PRs are broken do to secrets only in upstream repo