Mobbing Tools

Mob programming with remote teams poses a challenge for switching drivers. It can take time to restore the editor state from one driver to the next. This can cause frustration and interupt the flow state of the mob. One option is to have all participants remotely control a machine, but this poses many problems of its own, including input delay. This VSCode extension inserts itself into the mobbing workflow of using git to commit, push and pull code. It adds a button to save the current IDE state into the git commit message. The next driver can then run a command within the extension to restore their editor to the state of the previous driver based on the commit message, including opening files and restoring cursor positions. This saves time, reduces frustration and keeps the mob in a flow state.

Instructions

Prefix your branch with the JIRA ticket number (eg. SO-1001-Remove-Whitespace) for it to be parsed into the commit message.

Click the "MOB" button on the source control pane to populate the commit message with the files you have changed recently. Your commit message will be retained.

[SO-1001] Remove extra tabs ╠[["index.php",396,41]]╣

When it is your turn to drive, execute a git pull and then run "[MOB] Log Parse" from the actions pane to open the files in the last commits message to the specified line numbers.

Available Settings

• Pull file changes from the past X minutes into the commit message, this is recommended to be slightly higher than your standard mobbing time.

    "mobTools.mobTime": 15

• A regular expression to extract from the branch name the ticket number.

    "mobTools.pattern": "(SO-[0-9]*)"

• Ignore case in pattern.

    "mobTools.patternIgnoreCase": false

• Content to place in commit message.

    "mobTools.replacement": "[$1] "

Coming Soon

• Storing breakpoints
• PHPStorm Plugin

Installation

https://marketplace.visualstudio.com/items?itemName=sreed101.mobbing-tools