Closed
Conversation
Contributor
|
✅ All Jest tests passed! This PR is ready to merge. |
Member
Author
|
Hey @justin212407 , I understand your concern. I took up this issue because the existing PR (#4290) has been in draft for over a month without any progress. Since it seemed inactive, I worked on it to move things forward. Sorry for the inconvenience |
Contributor
|
✅ All Jest tests passed! This PR is ready to merge. |
Contributor
|
This pull request has been open for more than 60 days without any activity. It will be closed in 3 days unless the |
Contributor
|
Closed pull request due to inactivity for more than 63 days. |
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.
Pull Request: CI/CD Pipeline & GitHub Pages Deployment
📄 Description:
This PR addresses Issue #4284, introducing a CI/CD pipeline and automatic deployment to GitHub Pages.
Additionally, it resolves the problem where the deployment script was unintentionally triggered on forked repositories and pull requests, ensuring it only runs on merges to the
masterbranch of the main repository.✅ Checklist:
💡 What This PR Does:
masteronly.🔗 Related Issues:
Closes #4284
🧪 Testing Instructions:
master—the deployment should trigger.💬 Additional Notes:
If any issues arise during the deployment process, feel free to tag me for assistance!
@justin212407 please check out this