Skip to content
This repository has been archived by the owner on Nov 13, 2021. It is now read-only.

Projects which don't follow the expected commit message format #50

Open
schultyy opened this issue Jan 30, 2016 · 2 comments
Open

Projects which don't follow the expected commit message format #50

schultyy opened this issue Jan 30, 2016 · 2 comments
Assignees
Milestone

Comments

@schultyy
Copy link
Member

When I run semantic-rs on a project where the commit message format does not follow the Angular message style format, I get the following output:

[0] % cargo run -- -p ../Sokan
     Running `target/debug/semantic-rs -p ../Sokan`
semantic.rs 馃殌
Analyzing your repository
Current version: 0.1.0
Analyzing commits
Commits analyzed. Bump would be Major
New version would be: 1.0.0
Would write the following Changelog:
====================================
## v1.0.0 (2016-01-30)


====================================
Would create annotated git tag

We need to decide what should happen here. Do we generate a changelog or do we skip it?

@schultyy schultyy changed the title Project's which don't follow the expected commit message format Projects which don't follow the expected commit message format Jan 30, 2016
@schultyy schultyy modified the milestone: v0.1.0 Jan 30, 2016
@badboy
Copy link
Member

badboy commented Mar 11, 2016

This looks like there was no pre-existing tag and therefore a major bump was chosen. Not sure how to handle it.

No changelog? Changelog indicating "stable release"? Asking user to provide changelog?

@schultyy
Copy link
Member Author

Asking the user here sounds viable or if the user doesn't want to provide anything we then can drop in some default text like "stable release"

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

No branches or pull requests

2 participants