Skip to content

Configuration file not used with "gren release", but works with "gren changelog" #110

Closed
@ebousse

Description

@ebousse

To avoid having to always write the option --data-source=commits, I have created a configuration file called .grenrc.json with this content:

{
    "dataSource": "commits"
}

Then in the same folder I try to do a github release, and we see that it only searches for issues, not commits, therefore creating a release with 0 issues (because there is none):

$ gren release --override             

🤖  - Generate release notes:
===================================

Getting the list of releases : ...... (0.53 secs)
1 releases found

Getting tags : .... (0.35 secs)
Tags found: 2.4.0

Getting the tag dates ranges : .... (0.32 secs)
Creating the body blocks from releases:

Getting all closed issues : ...... (0.54 secs)
2.4.0 has 0 issues found	

Updating latest release : .... (0.34 secs)

2.4.0 has been successfully updated!

But if I do a git changelog, it does use the configuration file, because it correctly creates the list of commits in CHANGELOG.md.

Am I missing something?

thanks for your tool!

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy