GitHub Pages: Inconsistent Accessibility of Deployed Content After Artifact Deletion #138988
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi GitHub Community,
I’m deploying HTML report files to GitHub Pages using upload-pages-artifact@v3 and deploy-pages@v4, creating timestamped directories for each run (e.g., deployment/envname/{timestamp}).
Here’s what I’ve observed:
September 17: After running tests and uploading reports to GitHub Pages, the reports are accessible at their respective URLs.
September 18: After running tests again and uploading new reports, only September 18 reports are accessible at their respective URLs.
Artifact Deletion: When I delete the artifact for September 18, the reports with that timestamp remain accessible.
It seems that GitHub Pages maintains access to reports even after artifact deletion, but the reports become inaccessible after subsequent deployments.
Questions:
Artifact Deletion vs. Deployment: Is Github deleting the previous content and replacing it with the new content of the uploaded artifact?
Beta Was this translation helpful? Give feedback.
All reactions