Running tests on the `cli` environment causes coflicts with the `dev`
environment; the tests will log you out, modify the theme, etc.
Running tests on `tests-wordpress` will allow you to run tests along
with the `dev` environment without interference.
* Editor Sidebar: Make save panel text translatable
* add another missing translation fn
---------
Co-authored-by: Vicente Canales <vicente.canales@automattic.com>
* Remove font management code
Since the Font Management page is on its way out via deprecation, we
should remove the js code related to it.
* lint: Add missing dependency to useSelect
* Remove php files
* remove references to index.js and php files
* remove font library react app
* remove tests & data
* remove demo text input
* Removed some unused resources
* Returned the font management portion still needed
* removed unused utility functions and their unit tests (leaving a sample unit test in its place rather than dismantling the unit tests
* Returned create-panel to pre-fixed days
---------
Co-authored-by: Jason Crist <jcrist@pbking.com>
* Added tests to validate replacing theme namespace and refactored to support it
* Pass slug to patternize content when cloning theme
* Fixed creating of theme slug from name using no -'s to fix namespace swapping issue
* Update readme info with screenshot refs
* Update readme.md
* Add line breaks before lists in readme.txt
* Remove single list item
* Remove ref to pages
* Add fonts info
* Add install/uninstall fonts info
Co-Authored-By: Jason Crist <jcrist@pbking.com>
---------
Co-authored-by: Jason Crist <jcrist@pbking.com>
* Refactor GitHub release workflows
Refactor GitHub release workflows in order to comply with branch protection
rules. The new process:
1. Run the "Create new release PR" manually, selecting the release type
("major", "minor", or "patch"). This will create a new branch
including the Changelog update and the version bumo on the readme,
create-block-theme.php, and package.json files.
2. Merging the PR created on the previous step will trigger the deploy
workflow, which remains unchanged, except for the conditions added in
order for it to run only if the merged PR matches the characteristics of
automated release PR.
1. Fork this repo
2. Checkout this branch
3. Merge intro trunk on the fork
4. Run the workflow, a new PR should be created on the fork
5. Merge the PR; the automated deploy step will run. At this point, the
only thing that you'll be able to test on the fork is that the deploy
workflow correctly identifies the PR and branch as a new release. The
deploy itself requires credentials only available on the parent repo.
* add block themers as reviewers
* prefix tag with v
* add block themers as reviewers
* move version prefix to step where it's needed
* add deploy step name
* add trailing backslash
* remove reviewer
* add block-themers as reviewers for the release pr
* Fix changelog creation script
* don't reverse log, list by creation date instead
* remove comments
* remove debug comments
* remove debug console log
* exit on error retrieving changes
* remove redundant error print
* update screenshots and move to assets/
The directory changes follows the guidelines in the docs:
https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#where-do-i-put-my-files
* compress screenshots, format as jpg
* deps: add codemirror dependencies
* add user theme data endpoint
* Add code mirror editor for theme json data
* Moved json editor stuff to a modal class and started a resolvers file for API handling
* add theme name to editor modal title
* refactor fetchThemeJson
* reword from editor to inspector
* reword
* Update src/plugin-sidebar.js
Co-authored-by: Sarah Norris <1645628+mikachan@users.noreply.github.com>
* Update src/editor-sidebar/json-editor-modal.js
Co-authored-by: Sarah Norris <1645628+mikachan@users.noreply.github.com>
---------
Co-authored-by: Jason Crist <jcrist@pbking.com>
Co-authored-by: Sarah Norris <1645628+mikachan@users.noreply.github.com>
