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

Re-adding of the changelog command #2100

Open
Styyx1 opened this issue Oct 4, 2022 · 7 comments
Open

Re-adding of the changelog command #2100

Styyx1 opened this issue Oct 4, 2022 · 7 comments
Assignees
Labels
enhancement New feature or request

Comments

@Styyx1
Copy link

Styyx1 commented Oct 4, 2022

Describe the solution you'd like

  • The changelog command, while not the most clean as described by others, helped a lot to keep track of modlist updating. Even if it catches only the archive changes, it's way easier than writing down every change

Describe alternatives you've considered

  • Only alternative i know of would be manually writing down every change while updating the list. Definitely not ideal for big updates.

The command as it was (even though I know you are well aware of it)
wabbajack-cli.exe changelog --original "C:\Path\To\old\version.wabbajack" --update "C:\Path\To\new\version.wabbajack" -o FilenameOfTheOutput.md

@Styyx1
Copy link
Author

Styyx1 commented Oct 4, 2022

@EzioTheDeadPoet

@EzioTheDeadPoet
Copy link
Contributor

assigned erri as well since he made the feature in version 2.x

@Yagisan
Copy link

Yagisan commented Oct 24, 2022

I too, would really appreciate the return of this feature.

@erri120
Copy link
Member

erri120 commented Oct 24, 2022

Which information should the changelog contain? The original command generated a changelog that looked something like this:

### Updated

- Cool Mod: v1 -> v2

### Added

- BHUNP

### Removed

- CBBE 3BA

@Althro
Copy link

Althro commented Oct 24, 2022

Ideally something similar to that format with the mods under each section alphabetised. In terms of format, .md would be ideal for easy transfer onto github.

I know that the original one was not able to tell if you had updated something and removed the old version so that would be a "nice to have per se."

@Styyx1
Copy link
Author

Styyx1 commented Oct 24, 2022

I'd be happy if it 'only' catches changed archives like it did in 2.5.xx

Ideally the command would check if a removed archive got replaced by an archive with a similar name(aka update) tho, but if that's not easily doable, it would be a huge help to 'at least' catch every changed archive.

@erri120
Copy link
Member

erri120 commented Oct 24, 2022

I'd be happy if it 'only' catches changed archives like it did in 2.5.xx

Ideally the command would check if a removed archive got replaced by an archive with a similar name(aka update) tho, but if that's not easily doable, it would be a huge help to 'at least' catch every changed archive.

The old code had issues with updated mods because I rushed the feature for my Lotus modlist. Anyway, will try re-implementing this.

@EzioTheDeadPoet EzioTheDeadPoet added enhancement New feature or request needs-work Needs more work, or there are some concepts to discuss before it should be merged and removed needs-work Needs more work, or there are some concepts to discuss before it should be merged labels Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants