8000 GitHub - ewohltman/gitflux: Dynamic and Fluid Git Repo Handling - Written in Rust.
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ewohltman/gitflux

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

42 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation


Logo

Gitflux

Gitflux is an all in one conventional commit management and tag version manager.
Explore the docs »

View Demo · Report Bug · Request Feature

Table of Contents
  1. About The Project
  2. Getting Started
  3. Usage
  4. Roadmap
  5. Contributing
  6. License
  7. Contact
  8. Acknowledgments

About The Project

Gitflux is a work in progress proof of concept to further deepen my understanding of Rust, This tool is not intended for production usecases yet, but might be in the future. Please use at your own risk.

A lot of this README is still WIP so forgive any boilerplate still left over, thanks very much to othneildrew and his awesome readme template!

(back to top)

Usage

Tag bumping

Gitflux provides full incremental management of your tags in your repo using simple semver formatting, any git tags that cannot be parsed to a simple semver format will be ignored. You can initialise a simple tag pointing to the HEAD of your repository using

gitflux bump --init

You can also increase logging level by parsing the -v flag, this can be used incrementally to increase the logging level, each 'v' representing a greater level of logging, for example:

gitflux bump --init -vvvv

This will provide the highest level of verbosity (information).

inittag

Once you have initialised a semver tag, you can simply bump the patch level using

gitflux bump

bumptag

You can also pass the --tag-schema major|minor|patch or -t major|minor|patch flags to override the tag version that gitflux will bump your tag by:

gitflux bump --tag-schma minor

bumptagallvers

For more examples, please refer to the Documentation

(back to top)

Roadmap

  • Get tag bumping functionality up and running.
  • Create development branch
  • Tag releases from dev branch to master with gitflux
  • Configure global settings serde parsing.
  • CI/CD building for releases.
  • Lock step tag version with build / release version? Rust is doable, other apps maybe?
  • Implement conventional commit message manager and commit handling

See the open issues for a full list of proposed features (and known issues).

(back to top)

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

(back to top)

License

Distributed under the GNU GENERAL PUBLIC LICENSE. See LICENSE for more information.

(back to top)

Contact

Project Link: https://github.com/nrexception/gitflux

(back to top)

About

Dynamic and Fluid Git Repo Handling - Written in Rust.

Resources

License

Stars

Watchers

Forks

33CC

Releases

No releases published

Packages

No packages published

Languages

  • Rust 97.3%
  • Makefile 2.7%
0