-
Notifications
You must be signed in to change notification settings - Fork 31
Add website preview for all pull requests with GitHub Codespaces integration #1033
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
Conversation
Co-authored-by: yuhattor <[email protected]>
hey Copilot, could you check this? When running the apps, the error occured. we need hugo binary and set up them at the devcontainer file
|
Co-authored-by: yuhattor <[email protected]>
I've fixed the issue with the Hugo binary in Codespaces. The problem was that launch.json was configured to use Hugo as a Node.js binary, but Hugo isn't a Node.js application. I've changed launch.json to use a shell configuration instead of node, and improved the devcontainer.json to verify Hugo is properly installed during environment setup. The changes are in commit 7e6b92d. |
Please fix the following errors This codespace is currently running in recovery mode due to a configuration error. Please review the creation logs, update your dev container configuration as needed, and run the "Rebuild Container" command to rectify. Details
2025-05-20 07:22:45.736Z: Host information ================================================================================= ================================================================================= #1 [internal] load .dockerignore #2 [internal] load build definition from Dockerfile.extended #3 resolve image config for docker.io/docker/dockerfile:1.4 #4 [auth] docker/dockerfile:pull token for registry-1.docker.io #7 [internal] load metadata for docker.io/hugomods/hugo:base-0.133.1 #8 [auth] hugomods/hugo:pull token for registry-1.docker.io #10 [dev_containers_feature_content_normalize 1/3] FROM docker.io/hugomods/hugo:base-0.133.1@sha256:ca1b445276ed9a8e3d7e9fe7b3dca6ff7e21392b485339d555961c71855c4941 #12 [dev_containers_feature_content_normalize 3/3] RUN chmod -R 0755 /tmp/build-features/ #13 [dev_containers_target_stage 2/5] RUN mkdir -p /tmp/dev-container-features #14 [dev_containers_target_stage 3/5] COPY --from=dev_containers_feature_content_normalize /tmp/build-features/ /tmp/dev-container-features
|
Co-authored-by: yuhattor <[email protected]>
I've fixed the Codespaces configuration error in commit 1ed2cfd. The issue was with the base container image and Hugo installation. I've made these changes:
The container should now build properly without going into recovery mode. |
It looks pretty awesome, but there're some issues. debug doesn't show upIn the debug section on left pain, didn't show up. It only shows blank window. please set up properly ActionsYou don't need to deploy it everytime.
You don't need to use peter-evans' extension. you should use github cli to do so.
|
Co-authored-by: yuhattor <[email protected]>
... I've made the following changes to fix both issues in commit f0bd049:
The debug panel should now properly display the "Hugo Server" configuration, and the PR preview workflow is more efficient using GitHub CLI. |
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.
Functionality works. We can merge what's here. As a follow-on, let's see if we can get it to start the site automatically and put a link to the running site as a comment in the pull request. Not sure if this setup is possible with codespaces. Or if we just need branch deployment of github pages?
For now, I will merge it |
Website Preview for Pull Requests
This PR implements automatic website previews for all pull requests, making it easier for non-technical contributors to visualize and review changes to the website without needing to set up a local development environment.
Key Features
1. GitHub Codespaces Integration
.devcontainer
configuration for one-click development environment setup2. Automatic PR Preview Deployment
3. Documentation for Non-Technical Users
How to Use
For Non-Technical Contributors:
For Pull Request Reviews:
Wait for the "PR Preview" workflow to complete and a comment will be added with a link to view the website with the PR changes applied.
Fixes #1028.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.