test PR #109
Closed
test PR #109
Conversation
This file contains 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
…uilder and global block form. Testing still needed
…er this has been uninstalled in production.
…s, fallback images, change edit button text, and visual distinction of global reusable blocks
… when content preview is off
…evelop-feb1-2024 Backport: master hotfixes into develop
…usuable-global YALB-864/YALB-1650: Global reusuable blocks
* fix(YALB-520): fix embed source manager array EmbedSourceManager was not using the correct array to track the sources already used. This now references the instances array. * feat(YALB-520): add twig Url detector In order for dynamic link treatments to properly function, we need a Twig-based Url detector that can be utilized. This adds that function. This will take a Url and determine what type of link it is so that it can be properly treated.
… content type styling (yalesites-org#558)
…ge node path to URL alias (yalesites-org#559) * fix(YALB-1703): front page uses entity_autocomplete over linkit We are replacing linkit with an entity_autocomplete type in order for the front page to be set ultimately to a /node/{node_id} format over an alias. This will also attempt to convert those sites that might already have an alias set back to the /node/id format.
…ites-org#524) * feat(YALB-1681-admin-theme-updates): remove custom colors in favore of gin defaults * feat(YALB-1681-admin-theme-updates): set default admin theme to Auto instead of Dark * feat(YALB-1681): update colors - wip pr feedback fixes * feat(YALB-1681): update colors - wip pr feedback fixes * feat(YALB-1681): update placeholder variable --input-fg-color--placeholder: var(--gin-color-text) * feat(YALB-1681): update button text color gin dark mode in layout builder * feat(YALB-1681): update header and footer setting styles and levers styles * feat(YALB-1681): update chosen color styles for menu parent and search * feat(YALB-1681): update active border-color for alerts * feat(YALB-1681): update active text color for alerts * feat(YALB-1681): update hover color * feat(YALB-1681): upate colors for accessibility * feat(YALB-1681): upate colors for accessibility * feat(YALB-1681): upate chosen colors for dark mode only
…org#561) fix(YALB-1714): pin gin_lb module to ensure patch applies (yalesites-org#561)
…alesites-org#568) While fixed, smart_date 4.0.3 is not released yet, and we don't want to point to dev. This patch adds a dateFormatter to the class using it instead of relying on the parent class to provide this, causing the deprecation. Once 4.0.3 is released or we decide to bump to 4.1.x release, we can remove this.
* feat(YALB-680): add external source field * feat(YALB-680): add event subscriber * fix(YALB-680): moving control to sidebar with help text * feat(YALB-680): add external_source to search results --------- Co-authored-by: Joe Tower <[email protected]>
…tions Update release pull request action
Github Actions: fix retrieval of release branch in release pull request creation
Github Actions: minor changes pull request creation
Github Actions: set unique cache for release_pr job
…x_cache Github Actions: set persistent variable name for release_pr cache
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.
No description provided.