| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8" /> | |
| <title>SwiperJS - PBrocks - Sample</title> | |
| <link | |
| rel="stylesheet" | |
| href="https://cdnjs.cloudflare.com/ajax/libs/normalize/5.0.0/normalize.min.css" | |
| /> | |
| <link |
My objective is to have some production files ignored on specific branches. Git doesn't allow to do it.
My solution is to make a general .gitignore file and add .gitignore.branch_name files for the branches I want to add specific file exclusion.
I'll use post-checkout hook to copy those .gitignore.branch_name in place of .git/info/exclude each time I go to the branch with git checkout branch_name.
As of WordPress 5.8 release, we encourage using block.json file metadata as the canonical way to register block types. We have been working on Block Metadata specification for a few major WordPress releases, and we reached the point where all planned features are in place.
Example:
notice/block.json
{
"apiVersion": 2,
| #!/bin/bash | |
| ## Demo script to show how to leverage Azure DevOps CLI Extension to call DevOps REST API directly | |
| ## without the need for PAT token | |
| # configuration | |
| YOUR_AZURE_DEV_OPS_ORG='' | |
| YOUR_AZURE_DEV_OPS_PROJECT_NAME='' | |
| # Reverse Engineered this part by looking into Azure DevOps CLI Extension | |
| # https://github.com/Azure/azure-devops-cli-extension/blob/8cf32a41126b2b66f130843d4d16de19290052b9/azure-devops/azext_devops/devops_sdk/client.py#L71 |
| UPDATE wp_options SET option_value = replace(option_value, 'http://www.oldurl', 'http://www.newurl') WHERE option_name = 'home' OR option_name = 'siteurl'; | |
| UPDATE wp_posts SET guid = replace(guid, 'http://www.oldurl','http://www.newurl'); | |
| UPDATE wp_posts SET post_content = replace(post_content, 'http://www.oldurl', 'http://www.newurl'); | |
| UPDATE wp_postmeta SET meta_value = replace(meta_value,'http://www.oldurl','http://www.newurl'); |
| <?php | |
| /** | |
| * Post advanced form for inclusion in the administration panels. | |
| * | |
| * @package WordPress | |
| * @subpackage Administration | |
| */ | |
| // don't load directly | |
| if ( !defined('ABSPATH') ) |
| <?php | |
| /** | |
| * [pbrocks_check_title_filter] | |
| * | |
| * @param [type] $title [description] | |
| * @param [type] $post_id [description] | |
| * @return [type] [description] | |
| */ | |
| function pbrocks_check_title_filter( $title, $post_id = null ) { | |
| $current_post_type = get_post_type(); |
| <!DOCTYPE html> | |
| <html lang="en" > | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>Include WP</title> | |
| <style type="text/css"> | |
| html { | |
| box-sizing: border-box; | |
| } | |
| *, *:before, *:after { |
To set up php linting, you’ll want to install this PHP CodeSniffer repo and configure with this WordPress Coding Standards repo: . There are a number of ways to do this, whether direct download, Composer, Homebrew, Pear, etc. The following is what works for me on MacOS using Homebrew:
In a terminal window on your Mac, start by updating your Homebrew.
brew doctor
Then install the Code Sniffer:
| # 301 https://github.com/gerardroche/dotfiles |