Signing Git Commits & Tags with GPG2 and Verified on GitHub

So i got myself a MacBook PRO and finally made the switch to Mac world after a long time being a Windows user.

One of the things i have been meaning to do was to GPG sign my git commits. Setting up my new MacBook proves to be the perfect time and finally, i did it.

The web has a number of tutorials that shows how to sign git commits with GnuPG (GPG) but none with GPG version 2.

In this tutorial, i will be showing us how to sign Git commits and tag with GPG2.

FWIW, my Mac was running OSX Yosemite 10.10.3 at the time of writing. I am quite sure the guide below is pretty much the same for OSX 10.10 and greater.

For windows users, you should be able to follow this guide too. No? let me know in comments and I will see what I can do to help.

Ready? Let’s Go

Firstly, download and install GPG2 command line tools if you don’t have one installed already in your machine. You can test by running gpg2 command in terminal.

Open terminal

Run this command to generate a GPG key pair.

<br/>gpg2 --gen-key

gpg2 --gen-key

You will be asked to enter your name, email address. Ensure the email address matches your GitHub email address if you want Github to show your commits as verified otherwise ignore this advice.

To save your entry, type letter “O” and hit enter/return. You will be asking for a passphrase to continue. The passphrase will come in handy when signing your commits.

You should now see your GPG info displayed as follows:

<br/>pub rsa2048 2016-06-27 [S] 89456D5E759E1A6AEEAF590AEDC2699358643879<br/>uid [ultimate] Collins Agbonghama <me@w3guy.com><br/>sub rsa2079 2016-06-27 []

pub   rsa2048 2016-06-27 [S]       89456D5E759E1A6AEEAF590AEDC2699358643879 uid           [ultimate] Collins Agbonghama <me@w3guy.com> sub   rsa2079 2016-06-27 []

Run the command below to output your GPG key, substituting in your GPG key ID. Our tutorial generated GPG key ID is 89456D5E759E1A6AEEAF590AEDC2699358643879.

<br/>gpg2 --armor --export 89456D5E759E1A6AEEAF590AEDC2699358643879

gpg2 --armor --export 89456D5E759E1A6AEEAF590AEDC2699358643879

Copy your GPG key, beginning with -----BEGIN PGP PUBLIC KEY BLOCK----- and ending with -----END PGP PUBLIC KEY BLOCK-----.

Login to your GitHub account. In the top right corner of any page, click your profile photo, then click Settings.
Click SSH and GPG keys menu.

Click New GPG key.

In the “Key” textarea, paste the GPG key you copied earlier and save.

Telling Git about your GPG key

If you have forgotten your key ID, you can always retrieve it by running gpg2 --list-secret-keys command.

To set your GPG signing key in Git, run the command below, substituting in the GPG key ID you’d like to use. In this example, the GPG key ID is 89456D5E759E1A6AEEAF590AEDC2699358643879.

<br/>git config --global user.signingkey 89456D5E759E1A6AEEAF590AEDC2699358643879

git config --global user.signingkey 89456D5E759E1A6AEEAF590AEDC2699358643879

Signing commits and Tags using GPG

To sign your Git commits with GPG, add the -S flag to the git commit command like so:

<br/>git commit -S -m "your commit message"

git commit -S -m "your commit message"

To sign a tag, add -s flag to your git tag command like so:

<br/>git tag -s testtag

git tag -s testtag

After you create your commit and/or tags, provide the passphrase you set up when you generated your GPG key.

When you’ve finished creating commits locally, run the command below to push your commits and tag to your remote repository on GitHub.

<br/>git push --follow-tags

git push --follow-tags

Go to the tag and commit description page, you should now see the verified badge.

Common Problem and Solutions

If you got an error similar to the message below when trying to sign a Git commit or tag, the error is as a result of Git not able to find GPG in your machine.

<br/>error: cannot run gpg: No such file or directory<br/>error: could not run gpg.

error: cannot run gpg: No such file or directory error: could not run gpg.

Mind you, we installed GPG2 and not the version 1.x which by default is in /usr/local/bin/gpg2. Apparently, Git was looking into /usr/local/bin/gpg which doesn’t exist.

Running the command below explicitly tell Git where to find GPG.

<br/>git config --global gpg.program /usr/local/bin/gpg2

git config --global gpg.program /usr/local/bin/gpg2

Automatically Signing Your Git Commits

You can configure Git to automatically sign your commits (and tags) without specifying the -S (and -s) flags by running git config --global commit.gpgsign true or adding the following to ~/.gitconfig

<br/>[commit] gpgSign = true

gpgSign = true

Conclusion

I suck at writing conclusion. Please make do without one.

Read More

 Git, gpg, gpg2, Programming, signed git commit, Tools, Tutorials

Dealing With “Detached HEAD” State in Git

When you pull in branches from your repository remote or upstream by running say git pull origin master (to pull changes from origin master branch) or git pull upstream non-breaking-space to pull in non-breaking-space branch from upstream; checking out any of these remote branch (e.g. git checkout upstream/non-breaking-space) will result in detached HEAD state because they aren’t proper branches as they do not (currently) exist locally.

<br/>$ git checkout upstream/non-breaking-space<br/>Note: checking out 'upstream/non-breaking-space'. You are in 'detached HEAD' state. You can look around, make experimental<br/>changes and commit them, and you can discard any commits you make in this<br/>state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may<br/>do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at b1a3ef5... Issue #29 Fix bug with non-breaking spaces

$ git checkout upstream/non-breaking-space Note: checking out 'upstream/non-breaking-space'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example:   git checkout -b new_branch_name HEAD is now at b1a3ef5... Issue #29 Fix bug with non-breaking spaces

In a nutshell, detached HEAD state occurs when you try to checkout something that is not a local branch. It can be a commit, a tag or a remote branch.

when you make changes and commit them, these changes do not belong to any branch but that doesn’t mean the commits are deleted if you eventually switch to another branch.

As displayed in the command line interface, you have to check out a new branch to retain any changes and commits made like so:

<br/>git checkout -b new_branch_name

git checkout -b new_branch_name

Say you created a w3guy.md, staged and committed the change. And then switch to branch SupportElements.

<br/>echo 'hello w3guy readers' > w3guy.md git add w3guy.md git commit -am "commit made in detach head state" git checkout SupportElements

echo 'hello w3guy readers' > w3guy.md git add w3guy.md git commit -am "commit made in detach head state" git checkout SupportElements

To include the commit we made in detached head state above to our current branch; firstly, the SHA-1 checksum of the commit has to be known.

If you don’t know it, run git reflog show HEAD@{now} -10 to list ten revision history of HEAD.

<br/>$ git reflog show HEAD@{now} -10<br/>1b990a8 HEAD@{Sat May 28 22:24:06 2016 +0100}: commit: commit made in detach head state.<br/>b1a3ef5 HEAD@{Sat May 28 22:20:24 2016 +0100}: checkout: moving from SupportElement<br/>5845d85 HEAD@{Sat May 28 22:18:19 2016 +0100}: checkout: moving from SupportElement<br/>5845d85 HEAD@{Sat May 28 22:01:10 2016 +0100}: checkout: moving from b1a3ef5cbfb<br/>b1a3ef5 HEAD@{Sat May 28 21:12:46 2016 +0100}: checkout: moving from hum3 to ups<br/>b1a3ef5 HEAD@{Sat May 28 20:52:14 2016 +0100}: checkout: moving from b1a3ef5cbfb<br/>b1a3ef5 HEAD@{Sat May 28 20:51:34 2016 +0100}: checkout: moving from SupportElement<br/>5845d85 HEAD@{Sat May 28 20:31:35 2016 +0100}: checkout: moving from master to SupportElement<br/>38992da HEAD@{Sat May 28 19:53:37 2016 +0100}: checkout: moving from hum to master<br/>45a6b74 HEAD@{Sat May 28 19:48:06 2016 +0100}: checkout: moving from master to hum3

$ git reflog show HEAD@{now} -10 1b990a8 HEAD@{Sat May 28 22:24:06 2016 +0100}: commit: commit made in detach head state. b1a3ef5 HEAD@{Sat May 28 22:20:24 2016 +0100}: checkout: moving from SupportElement 5845d85 HEAD@{Sat May 28 22:18:19 2016 +0100}: checkout: moving from SupportElement 5845d85 HEAD@{Sat May 28 22:01:10 2016 +0100}: checkout: moving from b1a3ef5cbfb b1a3ef5 HEAD@{Sat May 28 21:12:46 2016 +0100}: checkout: moving from hum3 to ups b1a3ef5 HEAD@{Sat May 28 20:52:14 2016 +0100}: checkout: moving from b1a3ef5cbfb b1a3ef5 HEAD@{Sat May 28 20:51:34 2016 +0100}: checkout: moving from SupportElement 5845d85 HEAD@{Sat May 28 20:31:35 2016 +0100}: checkout: moving from master to SupportElement 38992da HEAD@{Sat May 28 19:53:37 2016 +0100}: checkout: moving from hum to master 45a6b74 HEAD@{Sat May 28 19:48:06 2016 +0100}: checkout: moving from master to hum3

Note: HEAD is actually a special type of reference that points to another reference. It may point to master or it may not (it will point to whichever branch is currently checked out).

With the SHA-1 checksum of the commit known, run git cherry-pick 1b990a8 to import or rebase the commit on the branch.

I wrote about cherry-pick in a previous post. You might want to check it out.

La Fin!

Read More

 Git, git branch, Programming

Medesun Online Medical Coding Training

Medical Coding and Billing Training for the AAPC CPC Exam
and AHIMA CCS Exam. Training is given by the World Record Trainer Dr Guptha
with 42 certifications.  Get the expert
training.

Training covers ICD-10, CPT and HCPCS in detail with 7 CPC
Mock exams.

Pass the Certification Exam or
100% Money Back**

Training by World Record Trainer-Dr
Guptha with 42 certifications

·        
Hostel facility Available for OUT of HYDERABAD students

·        
Day Scholar Batches in Ameerpet and Dilsukhngar.- Hyderabad

·        
7 Mock Exams-Extensive Preparation

·        
Intensive Study Program-8 hours per day with accommodation

·        
High-end training by most experienced and US Trainers

Call Now - 9885232990, 9966933693

Training is given in the following ways

1.      
Classroom Training for 2 months OR
2.      
Online training for 3 months
3.      
Or Fast track CPC Training for 10 days with FREE
Hostel Facility

DON’T Miss the offer, medical coding has high demand.
Medesun is located in Hyderabad. Pioneers in Medical coding, HL7 Training in India.

Why you should get Quality  Training:

1. Medical Coding is a skilled job

2. Knowledge of anatomy and physiology is must

3. The coder must carefully read the doctor’s and nurse’s notes to determine exactly what services the patient received

4. The coder must also understand private payer policies and government regulations for accurate coding and billing.

5. Inaccurate or incomplete coding costs the average doctor thousands of dollars a year in lost payments

6. Without competent coders, providers run the risk of losing revenue.

7. Medical coders should learn about the HIPAA compliance

8. Medical coders must follow ethics in coding

9. Should have complete understanding of Bundling and Unbundling

10. Should be expert in EM coding

11. Should be proficient in Medical Billing Guidelines

12. Should know the importance of coding the conditions that effect the Risk Adjustment

13. Medical coders must be DETAIL oriented

14. Medical coders should have good communication skills

15. Medical coders should master more than one coding speciality

16. Medical coders should be proficient in Coding Guidelines

17. Medical coders should be proficient in using the modifiers

18. Being a professional is also very important in medical billing and coding

19. Much of the information a medical billing and coding specialist handles is confidential. Ensure confidentiality and security

20. Able to manage stress. This profession requires long hours. It is a very stressful job. Hence, if you want to be in this field, you have to know how to manage stress while performing your duties.

Medesun Healthcare Solutions

405, Laxmi Nivas, Opp Green Park Hotel

Ameerpet. Beside DTDC courier.

Ph: 040-65266444, 9492021666, 9966933693

Assuring you of our best services and prompt attention at all times.

Read More

WordPress Customizer – Range Control with Selected Value Indicator

The WordPress customizer, formerly know as theme customizer allows administrator(s) and/or owner to customize and control the appearance of their WordPress powered website via an intuitive, click-and-drag interface.

The Customization API allows theme and plugin developers to customize and add controls to the “Appearance” → “Customize” admin screen.

In this tutorial, I won’t go over the steps on how to leverage or integrate customizer in your theme or plugin. Rather, i will be showing us how to create your own custom controls using a range input field as a case study.

By default, the customizer support all type of input fields including “range”. My gripe with the range input field is the lack of an indicator to show the current selected value. And this isn’t going to change anytime soon as the idea was rejected by WordPress core team.

I am not going to explain or step us through how the code work. Otto has that covered already.

Below is the PHP class for the range control.

<br/><?php<br/>class WP_Customize_Range_Control extends WP_Customize_Control<br/>{ public $type = 'custom_range'; public function enqueue() { wp_enqueue_script( 'cs-range-control', 'path/to/range-control.js', array('jquery'), false, true ); } public function render_content() { ?> <label> <?php if ( ! empty( $this->label )) : ?> <span class="customize-control-title"><?php echo esc_html($this->label); ?></span> <?php endif; ?> <div class="cs-range-value"><?php echo esc_attr($this->value()); ?></div> <input data-input-type="range" type="range" <?php $this->input_attrs(); ?> value="<?php echo esc_attr($this->value()); ?>" <?php $this->link(); ?> /> <?php if ( ! empty( $this->description )) : ?> <span class="description customize-control-description"><?php echo $this->description; ?></span> <?php endif; ?> </label> <?php }<br/>}

class WP_Customize_Range_Control extends WP_Customize_Control     public $type = 'custom_range';     public function enqueue()         wp_enqueue_script(             'cs-range-control',             'path/to/range-control.js',             array('jquery'),             false,             true         );     public function render_content()         ?>         <label>              if ( ! empty( $this->label )) : ?>                 <span class="customize-control-title"> echo esc_html($this->label); ?></span>              endif; ?>             <div class="cs-range-value"> echo esc_attr($this->value()); ?></div>             <input data-input-type="range" type="range" $this->input_attrs(); ?> value=" echo esc_attr($this->value()); ?>" $this->link(); ?> />              if ( ! empty( $this->description )) : ?>                 <span class="description customize-control-description"> echo $this->description; ?></span>              endif; ?>         </label>

And here is the JavaScript for range-control.js

<br/>(function ($) { $(document).ready(function ($) { $('input[data-input-type]').on('input change', function () { var val = $(this).val(); $(this).prev('.cs-range-value').html(val); $(this).val(val); }); })<br/>})(jQuery);

(function ($) {     $(document).ready(function ($) {         $('input[data-input-type]').on('input change', function () {             var val = $(this).val();             $(this).prev('.cs-range-value').html(val);             $(this).val(val);         });     }) })(jQuery);

Link to code on GitHub here

To use this range custom control class, add a control to your existing list of customizer controls like so:

<br/>$wp_customize->add_control( new WP_Customize_Range_Control( $wp_customize, 'content_font_size', array( 'label' => __('Font Size'), 'section' => 'section_id_to_use_here', 'settings' => 'content_font_size', 'description' => __('Measurement is in pixel.'), 'input_attrs' => array( 'min' => 10, 'max' => 80, ), ) )<br/>);

$wp_customize->add_control(     new WP_Customize_Range_Control(         $wp_customize,         'content_font_size',         array(             'label'       => __('Font Size'),             'section'     => 'section_id_to_use_here',             'settings'    => 'content_font_size',             'description' => __('Measurement is in pixel.'),             'input_attrs' => array(                 'min' => 10,                 'max' => 80,             ),         )

La Fin!

Read More

 customizer, Plugin Development, theme customizer, WordPress