-
Notifications
You must be signed in to change notification settings - Fork 267
Development Workflow
ryanoasis edited this page Nov 19, 2015
·
29 revisions
Only time-critical bugfixes go directly into master.
vim-devicons uses, at least to the best of my ability, semantic versioning.
todo - it is coming
- pull latest
master
branch - create new versioned branch "MAJOR.MINOR.PATCH", e.g.
0.5.3
- merge any PRs that go in the milestone
- commit any general issue fixes/updates that go in the milestone
- update the readme if applicable
- update the changelog
- regenerate the vim doc automagically with
html2vimdoc
- e.g.
cd ~
html2vimdoc/bin/python ./vim-tools/html2vimdoc.py ~/projects/vim-devicons/readme.md > ~/projects/vim-devicons/doc/webdevicons.txt
cd ~/projects/vim-devicons/
- push the new branch
- merge to
master
- create tag
- push lastest
master
This Wiki and the Readme contain a lot of information, please take your time to read the information.
If you run into any trouble, please start by looking in the FAQ.
There are very detailed Changelog and Release changes available.
Be sure to read the Contributing Guide before opening a pull request to Nerd Fonts.
-
Vote for VimDevIcons on vim.org