-
Updated
Jun 2, 2020 - Go
pair-programming
Here are 173 public repositories matching this topic...
-
Updated
Oct 19, 2020 - Shell
-
Updated
Oct 27, 2020
-
Updated
Oct 19, 2020 - Shell
-
Updated
Jul 7, 2020 - Elm
-
Updated
Mar 18, 2019 - JavaScript
-
Updated
Jul 16, 2020 - JavaScript
-
Updated
Oct 19, 2020 - JavaScript
-
Updated
Aug 21, 2020 - TypeScript
-
Updated
May 5, 2020
-
Updated
Dec 8, 2018 - Shell
-
Updated
Dec 14, 2017
-
Updated
Sep 1, 2017 - JavaScript
-
Updated
Jan 30, 2016 - Python
-
Updated
Mar 4, 2020 - JavaScript
Currently if you run git-mit outside the project directory, it will write to the users configuration.
This leads to a confusing situation where the configuration can fail to change or other weird behaviour. I can't think of any reason that we'd want to write to anything other than the local configuration.
To fix this change how we load the repository never to use anything other than the repo
It would be great to improve the space used by the contributors table by spreading it across each line.
My guess is that making a 5 column-wide is enough.
note: not sure if markdown will be the right tool, but always remember that HTML is also accepted
-
Updated
Sep 8, 2020 - JavaScript
-
Updated
Oct 26, 2020 - Python
-
Updated
Mar 16, 2020 - Shell
-
Updated
Feb 21, 2018 - Shell
When the setting commit.template
has never been set, Git returns an error when attempting to read it. It itself this is fine (it is how Git works after all), but it would be good if Pair coud handle the case more gracefully.
Workaround:
- run
git config --global commit.template ~/.GIT_TEMPLATE
- then run
pair with "Alice <alice@example.com>"
again!
-
Updated
Apr 15, 2020 - Shell
Improve this page
Add a description, image, and links to the pair-programming topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pair-programming topic, visit your repo's landing page and select "manage topics."
The
ContainerContext
class contains a workaround to bypass the JDK bug JDK-4787931.This bug should be fixed in JDKs > 7. We require at least a JDK 8.
Therefore we should be able to remove this