| [ | |
| { code: 'AD', label: 'Andorra', phone: '376', phoneLength: 6}, | |
| { code: 'AE', label: 'United Arab Emirates', phone: '971', phoneLength: 9}, | |
| { code: 'AF', label: 'Afghanistan', phone: '93', phoneLength: 9}, | |
| { code: 'AG', label: 'Antigua and Barbuda', phone: '1-268', phoneLength: 10}, | |
| { code: 'AI', label: 'Anguilla', phone: '1-264', phoneLength: 10}, | |
| { code: 'AL', label: 'Albania', phone: '355', phoneLength: 9}, | |
| { code: 'AM', label: 'Armenia', phone: '374', phoneLength: 6}, | |
| { code: 'AO', label: 'Angola', phone: '244', phoneLength: 9}, | |
| { code: 'AQ', label: 'Antarctica', phone: '672', phoneLength: 6}, |
Permission denied (publickey)
Seems a very common error in Gitlab.com or any Gitlab implementation. Last night I spend 4/5 hours without sleeping to solve the error.
Cloning into 'server'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Why standardize messages? Its clean. Easy to see what changed and when. As an up-and-coming developer, my repos will probably be potential employers first impressions of me. Clean code (proper indentions/spacing etc) and formatted commit messages help show that I care about my code.
The workflow is to create a .txt file as a template, and configure git to use that file as the default message when commiting.
The key is the character count. Note the dashed lines representing 50 characters for the summary, and 72 for the description.
####implimentation####
cd ~ #to confirm in the home directory