Message of the day:
Get involved with contributing to the SilverStripe core and wider module ecosystem! For some good issues to get started with contributing to SilverStripe, check out "Good first issues" listed here: https://silverstripe-github-issues.now.sh/?mode=easy
Ask questions or get help with things related to getting involved with SilverStripe core and module contribution!
You can ping SilverStripe team, and core team developers here for help with your pull requests, unit tests, yarn build-ing etc.
👋 hey again team, the SilverStripe open source team will be doing bugs again tomorrow (NZ time). we have a rough theme of subsites, fluent, asset-admin and open pull requests etc. sing out if anyone wants to get involved with us! cheers
i struggle trying to edit the patch in the interactive mode. I could never get it to accept my edits as valid, even if i just opened and saved with no changes, so if I couldn't do it using split chunk (hunk? i forget) i would just edit the file deleting the bits i didn't want in this commit, save, stage, then undo changes
I used to use
git add -p before they added it to vscode (and for a while after they added it because it has been quite buggy sometimes)
git add -p is super nice
I like using Fork, except for squashing
INTERACTIVE MODE under
git add --help
git add -p will get you that :)
and vscode supports adding partial files to staging which is (a little buggy but) very handy sometimes
well, actually i prefer the gui for adding files to staging