working on issue for deployment #436
Merged
Conversation
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.
Addresses issues related to the deployment process of our documentation site using GitHub Pages. The primary motivation behind these changes is to ensure that our deployment is robust and up-to-date with the latest changes in the
gh-pagesbranch.Key improvements include:
Git Configuration: We configure Git with a user name and email specific to GitHub Actions. This is necessary for any git operations performed during the CI workflow, ensuring that commits made by the bot are properly attributed.
Pulling Latest Changes: By pulling the latest changes from
gh-pagesbefore deployment, we reduce the likelihood of deployment conflicts and ensure that the most recent updates are included in the documentation.Force Deployment: The deployment command now includes the
--forceflag. This ensures that if there are any discrepancies between the local and remotegh-pagesbranches, the local version will overwrite the remote one, preventing deployment failures.Overall, these changes will streamline our deployment process and enhance the reliability of our documentation updates, ensuring that users always have access to the latest information.