Metadata-Version: 2.1
Name: bumpymcbumpface
Version: 0.1.0
Summary: Version-bump, tag, push, deploy to PyPI
Home-page: https://github.com/cjrh/boatymcboatface
Author: Caleb Hattingh
Author-email: caleb.hattingh@gmail.com
License: UNKNOWN
Project-URL: Bug Reports, https://github.com/cjrh/bumpymcbumpface
Project-URL: Source, https://github.com/cjrh/bumpymcbumpface
Description: .. image:: https://img.shields.io/pypi/pyversions/bumpymcbumpface.svg
            :target: https://pypi.python.org/pypi/${package}
        
        .. image:: https://img.shields.io/github/tag/cjrh/bumpymcbumpface.svg
            :target: https://img.shields.io/github/tag/cjrh/bumpymcbumpface.svg
        
        .. image:: https://img.shields.io/badge/install-pip%20install%20bumpymcbumpface-ff69b4.svg
            :target: https://img.shields.io/badge/install-pip%20install%20$bumpymcbumpface-ff69b4.svg
        
        .. image:: https://img.shields.io/pypi/v/bumpymcbumpface.svg
            :target: https://img.shields.io/pypi/v/bumpymcbumpface.svg
        
        .. image:: https://img.shields.io/badge/calver-YYYY.MM.MINOR-22bfda.svg
            :target: http://calver.org/
        
        
        Bumpy McBumpface
        ================
        
        When doing a new release, I got real tired of doing these things by hand:
        
        1. Update the version number of my package
        2. Commit that change to git
        3. Create a git tag with the new version
        4. Push the tag (and the new commit) to github
        5. Build new distributable packages: wheel (``.whl``) and source dist (``.tar.gz``)
        6. Upload the new packages to pypi
        
        *Bumpy McBumpface* will do these things, and will not ask questions.
        
        Requirements
        ------------
        
        You need to have these:
        
        - A file called ``VERSION`` in your project root, with MAJOR.MINOR.PATCH numbers
        - git
        - twine (set up *keyring* so that twine won't ask you for login/password)
        - pip
        - wheel
        
        You probably SHOULD BE in master branch branch when you run, but you
        only need to be in a branch that has a valid remote.
        
        Instructions
        ------------
        
        There are a several options, but only two important ones. By default,
        it will NOT do these things automatically:
        
            - Push to github
            - Deploy to PyPI
        
        This is just so that it defaults to "safe" by not affecting anything
        beyond your computer during testing. To make it do these things too,
        run it like this:
        
            $ bumpymcbumpface --push-git --push-pypi
        
        *Bumpy McBumpface* assumes that your version number is in the following
        format:
        
            MAJOR.MINOR.PATCH
        
        where each of the three fields is an integer. This also works for
        calendar-based versioning. By default, the PATCH value will be increased
        by 1 if you run without arguments. These two are the same:
        
            $ bumpymcbumpface --push-git --push-pypi
            $ bumpymcbumpface --push-git --push-pypi patch
        
        For a MINOR bump, change the work *patch* to *minor*. Likewise for *major*.
        
        Good luck!
        
Keywords: bump deploy version development
Platform: UNKNOWN
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Topic :: Software Development :: Build Tools
Classifier: License :: OSI Approved :: GNU Affero General Public License v3 or later (AGPLv3+)
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Description-Content-Type: text/x-rst
