Carlos Bravo
@cbravobernal on WordPress.org and Slack
Bio
- Member Since: February 22nd, 2017
- Location: Spain
- Website: carlosbravo.blog
- GitHub: cbravobernal
- Job Title: Software Engineer
- Employer: Automattic
Contribution History
Carlos Bravo’s badges:- Core Contributor
- Core Team
- Documentation Contributor
- Meta Contributor
- Test Contributor
- WordCamp Organizer
- WordCamp Speaker
-
Merged pull request #132 into WordPress/secure-custom-fields:
Bug: Fix repeater inner fields not showing in Field Group admin page. -
Submitted pull request #132 to WordPress/secure-custom-fields:
Bug: Fix repeater inner fields not showing in Field Group admin page. -
Merged pull request #131 into WordPress/secure-custom-fields:
Refactor: Update new metadata functions in some fields. -
Submitted pull request #131 to WordPress/secure-custom-fields:
Refactor: Update new metadata functions in some fields. -
Merged pull request #127 into WordPress/secure-custom-fields:
Fix: Add compatibility with Woo HPOS. Allow order fields. -
Merged pull request #130 into WordPress/secure-custom-fields:
Code Quality: Remove filename WPCS rule to be able to use PSR-4... -
Submitted pull request #130 to WordPress/secure-custom-fields:
Code Quality: Remove filename WPCS rule to be able to use PSR-4... -
Merged pull request #129 into WordPress/secure-custom-fields:
Specify the version refers to `SCF` in `@since` annotations -
Submitted pull request #127 to WordPress/secure-custom-fields:
Fix: Add compatibility with Woo HPOS. Allow order fields. -
Closed issue #85 on the WordPress/secure-custom-fields repository:
Shortcode Bug -
Merged pull request #114 into WordPress/secure-custom-fields:
Allow config errors to be display to users -
Merged pull request #124 into WordPress/secure-custom-fields:
Beta feature: Add endpoint to retrieve custom fields of a post type. -
Merged pull request #125 into WordPress/secure-custom-fields:
Editor Sidebar Experiment: Remove not needed function -
Submitted pull request #125 to WordPress/secure-custom-fields:
Editor Sidebar Experiment: Remove not needed function -
Closed pull request #123 on WordPress/secure-custom-fields:
Draft: Extend REST API types endpoint to include custom fields. -
Submitted pull request #124 to WordPress/secure-custom-fields:
Beta feature: Add endpoint to retrieve custom fields of a post type. -
Merged pull request #113 into WordPress/secure-custom-fields:
Framework and admin screen to add new features as opt-in -
Submitted pull request #123 to WordPress/secure-custom-fields:
Draft: Extend REST API types endpoint to include custom fields. -
Merged pull request #118 into WordPress/secure-custom-fields:
Update initialization of the `acfL10n` object to ensure it's available globally -
Merged pull request #115 into WordPress/secure-custom-fields:
Tools: Add prettier. -
Submitted pull request #115 to WordPress/secure-custom-fields:
Tools: Add prettier. -
Submitted pull request #113 to WordPress/secure-custom-fields:
Framework and admin screen to add new features as opt-in -
Merged pull request #106 into WordPress/secure-custom-fields:
Fix: Small fix on field link. -
Submitted pull request #106 to WordPress/secure-custom-fields:
Fix: Small fix on field link. -
Merged pull request #104 into WordPress/secure-custom-fields:
Refactor: Prevent some `undefined` array key warnings. -
Submitted pull request #104 to WordPress/secure-custom-fields:
Refactor: Prevent some `undefined` array key warnings. -
Merged pull request #103 into WordPress/secure-custom-fields:
E2E: Add field text testing. -
Submitted pull request #103 to WordPress/secure-custom-fields:
E2E: Add field text testing. -
Pull request #102 merged into WordPress/secure-custom-fields:
E2E: Add a trash all post types step. -
Submitted pull request #102 to WordPress/secure-custom-fields:
E2E: Add a trash all post types step. -
Merged pull request #101 into WordPress/secure-custom-fields:
Revert text domain change -
Pull request #98 merged into WordPress/secure-custom-fields:
E2E: Create a custom post type and use wp-scripts. -
Created issue #100 in the WordPress/secure-custom-fields repository:
E2E Testing Batch. -
Closed pull request #97 on WordPress/secure-custom-fields:
E2E: Refactor to use wp-scripts library. -
Submitted pull request #98 to WordPress/secure-custom-fields:
E2E: Create a custom post type and use wp-scripts. -
Closed pull request #96 on WordPress/secure-custom-fields:
E2E: Create a field group with a text input. -
Submitted pull request #97 to WordPress/secure-custom-fields:
E2E: Refactor to use wp-scripts library. -
Submitted pull request #96 to WordPress/secure-custom-fields:
E2E: Create a field group with a text input. -
Pull request #91 merged into WordPress/secure-custom-fields:
E2E: Setting up the environment. -
Submitted pull request #91 to WordPress/secure-custom-fields:
E2E: Setting up the environment. -
Pull request #84 merged into WordPress/secure-custom-fields:
Form Customizer: Refactor to WP and PHPStan standards, add tests. -
Pull request #89 merged into WordPress/secure-custom-fields:
Maintenance: Update package-lock and gitignore files. -
Submitted pull request #89 to WordPress/secure-custom-fields:
Maintenance: Update package-lock and gitignore files. -
Pull request #87 merged into WordPress/secure-custom-fields:
Playground: Add blueprint json asset file -
Submitted pull request #87 to WordPress/secure-custom-fields:
Playground: Add blueprint json asset file -
Pull request #86 merged into WordPress/secure-custom-fields:
Webpack configuration: update to be similar as Gutenberg / Core development -
Submitted pull request #86 to WordPress/secure-custom-fields:
Webpack configuration: update to be similar as Gutenberg / Core development -
Submitted pull request #84 to WordPress/secure-custom-fields:
Form Customizer: Refactor to WP and PHPStan standards, add tests. -
Pull request #81 merged into WordPress/secure-custom-fields:
Form Post: Fix PHPStan and PHPCS issues. -
Submitted pull request #81 to WordPress/secure-custom-fields:
Form Post: Fix PHPStan and PHPCS issues.
