-
Notifications
You must be signed in to change notification settings - Fork 0
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
Set up Resources section #13
Conversation
✅ Deploy Preview for tufresources ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Signed-off-by: sandra <[email protected]>
Out of curiosity, why are there two deployment previews? |
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 great!
Can I ask you a favor? Would you mind clicking all links that you added in this PR, which, I suppose, you copied from theupdateframework.io, and list the ones that don't work in a new issue in the upstream repo? --> https://github.com/theupdateframework/theupdateframework.io/issues
My mistake. I was having trouble configuring the Netlify build on the main branch so I added the preview to this branch too. But I'll delete it to avoid confusion. |
Sure. No problem. And thanks for the review. |
@chalin Created a new resources PR to solve commit issues in PR #12
The deploy preview from tufresources link is more accurate for this branch. Please review. Thanks