Read the statement by Michael Teeuw here.
Is there a tutorial for pushing development to Git?
-
I made some modifications I think are helpful to some modules and I plan to do the same to some default modules and maybe even MM itself.
From getting an account on github to making my efforts available for review or use, is there a tutorial or instructional on how to do it? If not, could someone help me?
-
@oldrocker not here, as it’s a general GitHub thing
-
make a fork of the thing you want to change
done on GitHub (push the fork button) -
git clone your copy/fork, not the original
-
make a new branch , any name
git checkout -b branch_name -
make and test your changes, make sure to update any files that require documenting your change
-
git commit your changes to the local repo( clone copies the hidden git repo)
-
git push your changes to your GitHub fork
-
submit a pull request to the original repo offering your changes
done on github
how to do each thing you will have to learn
https://medium.com/@urna.hybesis/pull-request-workflow-with-git-6-steps-guide-3858e30b5fa4 -
-
@sdetweil Thanks, seems straight forward enough. I already made some changes to my live version. Should I save the changed files in another location then remove the module and then proceed with the instructions?
-
@oldrocker that’s what I do.
move the current folder ( mv command)
clone the new
make the branch,
copy files from moved
then rest is as before -
@oldrocker
What I usually do is;- make a repository in GitHub regardless already real codes are written or not
- git clone the repository in local somewhere from GitHub.
- copy working files to there, new cloned directory, from local workspace
- git add and commit then push.
-
@MMRIZE Okay, I will give it a try. Thanks!
-
@oldrocker What modules have you worked on? I love to see upgrades to the system, even if they’re not accepted in the main module.