Skip to content
This repository was archived by the owner on Sep 20, 2022. It is now read-only.
This repository was archived by the owner on Sep 20, 2022. It is now read-only.

Useability; 1.Add Link to Github ReleaseNotes.md ; 2.Add Commit Range's Datestamps. #61

Open
@AnneTheAgile

Description

@AnneTheAgile

This project looks great to me! 2 things I'd like and perhaps can fix are ;

1.Add Link to Github ReleaseNotes.md
Right now https://github.com/JakeGinnivan/GitReleaseNotes/blob/master/ReleaseNotes.md
is not referenced from https://github.com/JakeGinnivan/GitReleaseNotes/releases

2.Add Commit Range's Datestamps.
On the notes page, https://github.com/JakeGinnivan/GitReleaseNotes/releases ,
each section includes a section similar to the below. Notice that the commit sha's do not show a date range. Since it may be that no work was done for some time after the prior release, or that work dates were overlapping, I find date stamps a helpful indicator to be able to look at logs for the items.

 0.4.0 (25 May 2014)

 - [#35](https://github.com/JakeGinnivan/GitReleaseNotes/pull/35) - When specifying 'FromTag all' the issues closed for the first tag aren't included contributed by Petrik van der Velde ([pvandervelde](https://github.com/pvandervelde))

Commits: 3cb3104f89...ae4bda5b0b

2A. If we had the Diff feature in this ticket that would also be great;
Commit range should link to GitHub compare enhancement
#44 opened on Jun 25 by JakeGinnivan

2B. FYI, this ticket is slightly related to putting an issue ID in a branch name.
Support Issue numbers in branch names
#19 opened on Dec 17, 2013 by JakeGinnivan

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions