Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an extension to generate a changelog #59

Open
ggrossetie opened this issue Mar 13, 2016 · 4 comments
Open

Create an extension to generate a changelog #59

ggrossetie opened this issue Mar 13, 2016 · 4 comments

Comments

@ggrossetie
Copy link
Member

The idea is to be able to generate a changelog:

We could even support multiple SCM. For instance, if we want to display the Git changelog of a project, between master and version 1.0.0:

changelog:git[master..v1.0.0]
@mojavelinux
Copy link
Member

This would be insanely useful.

Here are a few ideas of what to include:

Per tag:

  • version number
  • release date
  • release author

Per item:

  • summary
  • issue number(s)
  • commit author(s)
  • category

Summary:

  • link to full diff
  • link to milestone in issue tracker
  • link to git tag

The hardest part is the category. This is where some conventions in the project would help. One way is to lookup the referenced issue and grab its label(s). Another idea is to include a category label in the commit messages. I picked up this idea from https://www.youtube.com/watch?v=m0_C2cfM9IM.

@mojavelinux
Copy link
Member

Perhaps the target should be the tag and the service/source part of the attribute list.

changelog::v1.5.3..v1.5.4[source=git]

or simply

changelog::v1.5.3..v1.5.4[git]

or, perhaps, the version range should be implied (going one back)

changelog::v1.5.4[git]

I might even argue the case that the service/source should be part of the macro name:

git-changelog::v1.5.4[]

@ggrossetie
Copy link
Member Author

Thanks Dan for sharing your ideas, lot of great stuff 😄

the version range should be implied (going one back)

This can be tricky because it depends on project's conventions.

issue number(s)

We could also automatically add a link on the issue tracker but again it depends on project's conventions.

@mojavelinux
Copy link
Member

mojavelinux commented Mar 14, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants