Open
Conversation
itslenny
force-pushed
the
lenny/fix-docs-pages-deploy
branch
from
08194a1 to
bbc0629
Compare
itslenny
force-pushed
the
lenny/fix-docs-pages-deploy
branch
from
bbc0629 to
75aea93
Compare
Coverage Report for CI Build 25138504624Coverage remained the same at 71.891%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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
2 participants
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.
What kind of change does this PR introduce?
Chore
What is the current behavior?
Uses 3rd party action which depends on deprecated node to deploy github pages
What is the new behavior?
Use github official github pages action
Additional context
https://docs.github.com/en/pages/getting-started-with-github-pages/using-custom-workflows-with-github-pages