Commands for groups

[goldbocman]

Added new commands for easier groups manipulation:

• /automodpack group - List of modpack groups. --full for more details .
• /automodpack group new "groupName" - Create new group.
• /automodpack group remove "groupName" - Remove already existing group. --yes to delete immediately, without confirming.

[Skidamek]

https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase

[Skidamek]

Sorry, that just triggers me

[suerion]

Sorry, that just triggers me

buuuut :) most of the people don't work with rebasing, they commit with there IDE directly :)

[Skidamek]

then just start commiting from main and not from some very old snapshot

[Skidamek]

plus, any ai agent could just fix it for you in a minute and force push it

[Skidamek]

Thank you, I hope you learnt something useful.

However tbch I don't really like this, I don't get the point of this, isn't it already easier to just go in the config and add or remove stuff or create a new folder and add there stuff? you cant do much through commands here, like literally what those do now is just adding or removing is a single entry from a list in the config.

Only the group listing seems useful, but I don't think chat is a great way of communication for that either.

[suerion]

plus, any ai agent could just fix it for you in a minute and force push it

@Skidamek

I understand rebasing, but I usually keep my feature branch synchronized with main by merging the latest changes into it and committing normally. That workflow is easier for me because it is how I originally learned Git, and it is also the standard workflow offered directly by most IDE integrations.

I know that rebasing can create a cleaner history, especially when working alone. However, rebasing and force-pushing a branch that other people are also using can cause problems because it rewrites the commit history. On my own feature branch it would be fine, but I personally prefer merging and regular commits.

I also would not use an AI agent just to rewrite and force-push the branch. I mainly use AI for debugging or language differences, so that everyone can understand what I mean.

I do not want to start an argument about it. I just wanted to explain my workflow and why I use it. I completely understand your point when someone is working alone and wants a cleaner history.

@goldbocman thanks for working on this features :)

[goldbocman]

Thank you, I hope you learnt something useful.

However tbch I don't really like this, I don't get the point of this, isn't it already easier to just go in the config and add or remove stuff or create a new folder and add there stuff? you cant do much through commands here, like literally what those do now is just adding or removing is a single entry from a list in the config.

Only the group listing seems useful, but I don't think chat is a great way of communication for that either.

Yep, setup should be and already is in configs. But manually copying and creating/deleting groups - it increases chances to make an error. You can forget about adding group's config, or clear folders of a fresh duplicated from "main" group's files. All "group new" do is:
a) paste clear group cfg to server.json
b) clear clear folder structure for that group

no manual creating and keeping an eye for naming, formatting