Creating an issue fork to contribute to a Drupal module, without getting confused.
(This cheat sheet is for myself. Fellow cheaters welcome.)
Check the branch that the issue is against— even if you filed the issue yourself, it should have defaulted to the branch people should be working on.
Go to the module page and scroll down, if you are lucky there will be a dev release toward the bottom, for example "Development version: 2.0.x-dev", which you can click into and copy the composer command.
(If there is not a dev release, you'll have to look at Development in the sidebar, click through "Source code" and copy from the Code dropdown either the URL under Clone with SSH or Clone with HTTPS, and git clone that into a modules.
Press the Create issue fork button and wait a minute.
Press the "Show commands" link, and copy-paste the commands in the Add & fetch this issue fork’s repository
And then copy-paste the commands from Check out this branch for the first time
Assign to yourself in "Issue metadata fieldset and save the issue form with any comment about how you plan to work on this that you hope somebody might provide feedback on or as a reminder to your later self.
Comments
Add new comment