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

Add "Add" command #34

Closed
SeanTAllen opened this issue Oct 31, 2019 · 1 comment · Fixed by #50
Closed

Add "Add" command #34

SeanTAllen opened this issue Oct 31, 2019 · 1 comment · Fixed by #50

Comments

@SeanTAllen
Copy link
Member

There is currently no way to use the changelog-tool to add a new changelog entry.

The add command should take:

  • the section to update (added, fixed, changed)
  • entry text

and then update the appropriate section by adding the new entry at the end of the section.

Should accept the

   -f, --file=CHANGELOG.md    Path of the changelog
   -e, --edit=false           Modify the changelog file

options that we use for other possible modifications command.

ordepdev pushed a commit to ordepdev/changelog-tool that referenced this issue Nov 9, 2019
ordepdev pushed a commit to ordepdev/changelog-tool that referenced this issue Nov 9, 2019
ordepdev pushed a commit to ordepdev/changelog-tool that referenced this issue Nov 9, 2019
ordepdev pushed a commit to ordepdev/changelog-tool that referenced this issue Nov 9, 2019
ordepdev pushed a commit to ordepdev/changelog-tool that referenced this issue Nov 9, 2019
@Theodus Theodus self-assigned this Nov 9, 2019
Theodus added a commit that referenced this issue Nov 9, 2019
The new `add` command has resulted in some workarounds for the original
assumption that the "unreleased" release is either nonexistent or empty
in many code paths. This is resolved by adding a separated class,
`Unreleased`, that enforces the requirement that this part of the
changelog must contain all sections if it exists.

Closes #34
SeanTAllen pushed a commit that referenced this issue Nov 9, 2019
The new `add` command has resulted in some workarounds for the original
assumption that the "unreleased" release is either nonexistent or empty
in many code paths. This is resolved by adding a separated class,
`Unreleased`, that enforces the requirement that this part of the
changelog must contain all sections if it exists.

Closes #34
@Theodus Theodus removed their assignment Nov 9, 2019
@Theodus
Copy link
Contributor

Theodus commented Nov 9, 2019

Thanks again to @ordepdev for doing most of the heavy lifting on this one!

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

Successfully merging a pull request may close this issue.

2 participants