Giter Club home page Giter Club logo

git-releaselog's People

Stargazers

 avatar

Watchers

 avatar  avatar

git-releaselog's Issues

Print the next tag name instead of "Unreleased"

When generating the Changelog with a to_ref which does not exist as tag, we could assume that that is the name for the next release and thus print the name instead of "Unreleased"

E.g. See https://github.com/iv-mexx/git-releaselog/blob/master/CHANGELOG.md
This Changelog was generated for the release "0.7.0", but before the tag was created (--> The updated changelog should be part of the tag, so the tag needs to be created later than the changelog).

Rename the project

Since git-changelog is already taken on rubygems, it would probably be good to change the project's name rather sooner than later.

Some suggestions to get us started (all of them are available on rubygems), but please feel free to pick whatever you like: gitch, git-releaselog, git-whatsnew

Option to skip Version Header

Currently, the Version Header (Current-Tag + Date) is always generated. When using the Changelog in a Github Release Message, the information is redundant, because the version is already a separate attribute of the release.

So, it would be nice to be able to skip the Version Header

NoMethodError when not providing a to_ref in case no to_ref argument is given on CLI execution

The stripping of from_ref_name and to_ref_name from 6b24431 causes errors in case one of them is nil.

For example with the execution of git-releaselog 0.10.0 (without a to_ref, the expectation being that a releaselog is generated from 0.10.0 up to the current commit):

git-releaselog-0.7.1/lib/git-releaselog.rb:12:in `generate_releaselog': undefined method `strip' for nil:NilClass (NoMethodError)

In Rails you could think about handling such cases with NilClass.try?, but Iโ€™m not perfectly sure this is how it should be handled here.

Changelog uses date from wrong tag for release message

When calling git-changelog for my project like this: git-changelog 0.9.0 0.8.0 --format slack it contains a line like the following: Version 0.9.0 (_03.09.2015_)

But 03.09.2015 is in fact the date of the tag 0.8.0. Instead, I would have expected it to pick up the date from the tag 0.9.0, which would be 17.09.2015.

I think the cause may be this line and this line (this should probably be DRYed up by abstracting the information retrieval to a new class for example), which should be str << " (_#{@commit_from.time.strftime("%d.%m.%Y")}_)" (from instead of to) instead.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.