TL;DR Script for updating PeopleGoal Feedback Questions per User
Discovered PeopleGoal recently.
I like codifying peoples' job responsibilities via the Feedback Question but for 33 reports in my org, neither I nor my managers can be bothered to key-in each via the UI.
| ## Prefixes | |
| [del]: Delete code | |
| [dist]: Changes to submodules, version bumps, updates to package.json | |
| [doc]: Updates to documentation | |
| [feat]: New feature | |
| [fix]: Bug fixes | |
| [infra]: Infrastructure changes | |
| [merge]: Resolved git merge from upstream or otherwise | |
| [nit]: Small changes: syntax, typos | |
| [refact]: Refactor |
| [test]: Update test/* files | |
| [dist]: Changes to submodules, version bumps, updates to package.json | |
| [minor]: Small changes | |
| [doc]: Updates to documentation | |
| [fix]: Bug fixes | |
| [bin]: Update binary scripts associated with the project | |
| [refactor]: Refactor of existing code | |
| [nit]: Small code review changes mainly around style or syntax | |
| [feat]: New features |
Let's say the plugin is at a GitHub URL https://github.com/manasthakur/foo.
First get the plugin by either cloning it (git clone https://github.com/manasthakur.foo.git) or simply downloading it as a zip (from its GitHub page).
Adding a plugin in Vim is equivalent to adding the plugin's code properly into its runtimepath (includes the $HOME/.vim directory by default).
For example, if the layout of a plugin foo is as follows:
foo/autoload/foo.vim
foo/plugin/foo.vim
| " A minimal vimrc for new vim users to start with. | |
| " | |
| " Referenced here: http://www.benorenstein.com/blog/your-first-vimrc-should-be-nearly-empty/ | |
| " Original Author: Bram Moolenaar <Bram@vim.org> | |
| " Made more minimal by: Ben Orenstein | |
| " Last change: 2012 Jan 20 | |
| " | |
| " To use it, copy it to | |
| " for Unix and OS/2: ~/.vimrc |
