[GitHub] Uploads the Build Artifacts To Simple Website Using GitHub P…#910
Closed
OmarAglan wants to merge 1 commit intoTheSuperHackers:mainfrom
Closed
[GitHub] Uploads the Build Artifacts To Simple Website Using GitHub P…#910OmarAglan wants to merge 1 commit intoTheSuperHackers:mainfrom
OmarAglan wants to merge 1 commit intoTheSuperHackers:mainfrom
Conversation
Skyaero42
reviewed
May 24, 2025
73f803f to
24ddfd2
Compare
Author
|
Updated To only Keep 5 artifact, so the storage doesn't get overwhelmed. |
Author
|
Closing as looks like #929 is better method of doing this. |
This file contains hidden or 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
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.
This pull request enhances the CI workflow by introducing functionality to manage and deploy build artifacts to GitHub Pages. The most significant changes include adding permissions for
pagesandid-token, creating a new job to prepare GitHub Pages content, and adding a deployment job for publishing to GitHub Pages. This happens only if there is a successful build, and only on the last commit on main. This makes it faster for others to test this by downloading the built artifact.Permissions Updates:
pages: writeandid-token: writepermissions to the workflow to enable artifact management and deployment to GitHub Pages. (.github/workflows/ci.yml, .github/workflows/ci.ymlR6-R7)New GitHub Pages Workflow:
prepare-gh-pagesjob that:index.htmlfile listing historical builds and their artifacts..github/workflows/ci.yml, .github/workflows/ci.ymlR140-R277)deploy-gh-pagesjob to publish the prepared content to GitHub Pages, ensuring the latest artifacts are accessible. (.github/workflows/ci.yml, .github/workflows/ci.ymlR140-R277)for example, on my repo, the website looks like this:
https://omardev.engineer/GeneralsGameCode/
Targets issue #886