feat(ci): move to mc-modpack-kit

[jh-devv]

No description provided.

[jh-devv]

@Aninuscsalas You have to set the Modrinth ID and TOKEN in the settings
Also allow "Allow PR's to be managed with actions"

[jh-devv]

@Aninuscsalas Can't maybe yet merge cause ParadigmMC/mc-modpack-kit#49

[jh-devv]

@Aninuscsalas This should be pretty much complete (still have to add some stuff) but I want to ask something:

Does the version of the pack need to be different for the Forge and Quilt version?
Because for that, we would need ParadigmMC/mc-modpack-kit#49

[Aninuscsalas]

Does the version of the pack need to be different for the Forge and Quilt version? Because for that, we would need jh-devv/mc-modpack-kit#49

I'm still not sure what to do. I think its better to wait because in my test repos modrinth publishing/builing often fails, or skips everything. Im going to some testing with other packs before this one gets merged

[jh-devv]

Hmm, weird? Have you read the README?

[jh-devv]

Does the version of the pack need to be different for the Forge and Quilt version? Because for that, we would need jh-devv/mc-modpack-kit#49

I'm still not sure what to do. I think its better to wait because in my test repos modrinth publishing/builing often fails, or skips everything. Im going to some testing with other packs before this one gets merged

Could you share a test repo of yours?

[jh-devv]

@Aninuscsalas First, sorry for so late response!
I got it working? Perhaps you had older releases but it just works fine? Can yoy recheck this?

[jh-devv]

This theorically should be now working (the release please things just means you can bump one part of the monorepo)
Shoudl work!

[Aninuscsalas]

This theorically should be now working (the release please things just means you can bump one part of the monorepo) Shoudl work!

Should we try merging it? I have added the secrets to the repo. I guess the versioning can restart from 0.1.0... Im still not sure how should i style commit names, chore(quilt):, and feat(forge): can work fine but im not sure that listing all the updated mods separately or just saying "Updated mods" is a better idea.

[jh-devv]

Should we try merging it? I have added the secrets to the repo. I guess the versioning can restart from 0.1.0... Im still not sure how should i style commit names, chore(quilt):, and feat(forge): can work fine but im not sure that listing all the updated mods separately or just saying "Updated mods" is a better idea.

@Aninuscsalas Yea, but you could just try to run the version workflow right away and set it to just some value (e.g. fabric, it does not support currentry different versions for different components) and for the version set 0.1.0 if you want that!

And for the mod commits, I would use it like:
For updates:
chore(fabric): Update mods
For bigger mod changes (e.g. adding or removing)
feat(fabric): Added mods or feat(fabric): Added Fabric API
Its pretty much how'd you like it!

Hope this helps
jh-devv

[jh-devv]

@Aninuscsalas Now my project uses commits like

• feat(modpack/<mod>): <description> for adding new features, configs or content.
• chore(modpack/<mod>): <description> for routine maintenance tasks or cleanups.
• update(modpack/<mod>): update <mod> for updating mods to newer versions.
• mod(modpack/<mod>): add <mod> for introducing new mods to the modpack.

[Aninuscsalas]

I'm gonna probably try to merge this this in the next few days 🙃

[jh-devv]

@Aninuscsalas now just run the set version workflow ;3

[Aninuscsalas]

@Aninuscsalas now just run the set version workflow ;3

can i do that before merging? (im new to github)

[jh-devv]

@Aninuscsalas now just run the set version workflow ;3

can i do that before merging? (im new to github)

You can do it right after or I can do it :3

[jh-devv]

https://github.com/orgs/community/discussions/25488 @Aninuscsalas