You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for making this tool. It's been very helpful for growing collaborative practices in my org.
A paper cut felt among engineers relates to the practice of aliasing git with git-together and interacting with repositories that have opted out if git together config. The UX looks a bit like this atm
git commit -m "making changes"
Error: error getting git config for'git-together.active'
Caused by: config value 'git-together.active' was not found; class=Config (7); code=NotFound (-3)
which causes friction and friction is a turn off for wider adoption. It would be great if instead this tool emitted a warning so that its visible that this repo a person is interacting with is not yet configured for git-together but allowed the git process to continue
The text was updated successfully, but these errors were encountered:
Thanks for making this tool. It's been very helpful for growing collaborative practices in my org.
A paper cut felt among engineers relates to the practice of aliasing git with git-together and interacting with repositories that have opted out if git together config. The UX looks a bit like this atm
which causes friction and friction is a turn off for wider adoption. It would be great if instead this tool emitted a warning so that its visible that this repo a person is interacting with is not yet configured for git-together but allowed the git process to continue
The text was updated successfully, but these errors were encountered: