-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support Multiple PR Previews #70
Conversation
Your site is deployed at https://lfortran.github.io/pull_request_preview/lfortran/70 |
Your site is deployed at https://lfortran.github.io/pull_request_preview/lfortran/70 |
It seems to work after commit Create .nojekyll. The |
Your site is deployed at https://lfortran.github.io/pull_request_preview/lfortran/70 |
Your site is deployed at https://lfortran.github.io/pull_request_preview/lfortran/70 |
This is ready. Please review and share feedback. |
@@ -0,0 +1 @@ | |||
{ "id": "c969e0bc3" } |
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.
With this PR, we are now maintaining the latest_commit
in this utils/commit.json
file. (It is now separate from the build
script).
Currently, after a PR is closed/merged, its preview folder needs to be manually deleted. (Automatic deletion of the preview folder is yet to be supported.) |
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.
I think this looks good. After you merge, can you please also document in the README what the process is to update LFortran?
towards #67