Conversation
pantierra
force-pushed
the
feature/avoid-gh-pages
branch
from
609dbec to
51f7d17
Compare
pantierra
force-pushed
the
feature/avoid-gh-pages
branch
from
51f7d17 to
695529e
Compare
yellowcap
approved these changes
Jul 18, 2025
Member
yellowcap
left a comment
yellowcap
left a comment
There was a problem hiding this comment.
I agree with this, we should not have another broken verison lingering around. 👍🏽
danielfdsilva
approved these changes
Jul 21, 2025
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
3 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.
Cleanup PR.
I suggest we don't deploy anymore to gh-pages. This was used for testing purposes, but we are now having a live system with a specific URL and semi-private data.