ylib/nerdtree
1
0
Fork 0
mirror of https://github.com/preservim/nerdtree.git synced 2024-11-25 17:57:24 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
f8aa749985
nerdtree/.github/PULL_REQUEST_TEMPLATE.md

17 lines
851 B
Markdown
Raw Normal View History

Update Changelog and create PR Template (#1007) * Update CHANGELOG and change it to Markdown format. * Add PR template with checklist for advancing the version number. * Update version number. * Change PR number in change log and PR template.
2019-06-27 13:28:45 +08:00
### Description of Changes
Expand functionality of <CR> mapping (#1011) * Define default values for new variables governing new "Default Open". "Default Open" means to open a file with the Enter key (which of course can be changed.) The key can be changed in the vimrc, and there is a variable for specifying the Opener parameters for opening the node. This lets the user decide whether Enter (or another key) will open a file in the current tab or a new one, and whether or not to open the file again in the tab or jump to a window where the file is already open. * Remove the old mapping for <CR>, a duplicate of 'o'. <CR> will be defined like all the other keys, in plugin/NERD_tree.vim * Assign functions to the new <CR> key mapping. Three separate functions handle directories, files, and bookmarks. * Rename variables: NERDTreeCustomOpen and NERDTreeCustomOpenArgs * Add documentation for NERDTreeCustomOpenArgs and NERDTree-<CR>. * Make key mapping variables be indexed in the Vim help * Remove angle brackets from <CR> to see if help navigation improves. * Rename functions from defaultOpen... to customOpen... * Use separate options for file and directory nodes. * Update documentation for separate file/directory options. * Update version number and change log. * Change CR to <CR> in help tags. * Fix missing backtick in patch number. * Update the quickhelp text. * Update Pull Request template. * Update change log with simpler formatting of patch number. * Get NERDTree version number directly from CHANGELOG.md * Reformat the lists of contributors in the Change Log. * Initialize the version text, just in case the while loop finds nothing.
2019-07-02 10:13:20 +08:00
Closes # <!-- Issue number this PR addresses. If none, remove this line. -->
Update Changelog and create PR Template (#1007) * Update CHANGELOG and change it to Markdown format. * Add PR template with checklist for advancing the version number. * Update version number. * Change PR number in change log and PR template.
2019-06-27 13:28:45 +08:00
---
### New Version Info
Update version number instructions in PR template and change log.
2019-10-11 22:44:25 +08:00
#### Author's Instructions
- [ ] Derive a new `MAJOR.MINOR.PATCH` version number. Increment the:
- `MAJOR` version when you make incompatible API changes
- `MINOR` version when you add functionality in a backwards-compatible manner
- `PATCH` version when you make backwards-compatible bug fixes
Update PR template with instructions to tag the release.
2019-08-19 21:36:50 +08:00
- [ ] Update [CHANGELOG.md](https://github.com/scrooloose/nerdtree/blob/master/CHANGELOG.md), following the established pattern.
Update version number instructions in PR template and change log.
2019-10-11 22:44:25 +08:00
#### Collaborator's Instructions
- [ ] Review [CHANGELOG.md](https://github.com/scrooloose/nerdtree/blob/master/CHANGELOG.md), suggesting a different version number if necessary.
- [ ] After merge, tag the merge commit, e.g. `git tag -a 3.1.4 -m "v3.1.4" && git push origin --tags`
Reference in New Issue Copy Permalink