git cli workflow #129

New Issue

2021-09-18T15:14:27Z

SoniEx2 commented

2021-09-18 15:14:27 +00:00

(Migrated from github.com)

We'd like to propose the following git CLI workflow for starting a new mod:

mkdir mymod
cd mymod
git init
git pull --allow-unrelated-histories https://github.com/FabricMC/fabric-example-mod/ 1.17
edit LICENSE and README.md
do your stuff here

as well as the following git CLI workflow for updating a mod:

git branch -m 1.16
git checkout -b main
git pull --allow-unrelated-histories https://github.com/FabricMC/fabric-example-mod/ 1.17
fix merge conflicts (mainly with LICENSE and README) and do your stuff here

We'd like to propose the following git CLI workflow for starting a new mod: ``` mkdir mymod cd mymod git init git pull --allow-unrelated-histories https://github.com/FabricMC/fabric-example-mod/ 1.17 edit LICENSE and README.md do your stuff here ``` as well as the following git CLI workflow for updating a mod: ``` git branch -m 1.16 git checkout -b main git pull --allow-unrelated-histories https://github.com/FabricMC/fabric-example-mod/ 1.17 fix merge conflicts (mainly with LICENSE and README) and do your stuff here ```

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Steven/fabric-example-mod#129