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
Hope you guys at TomTom are all doing well. I am starting to implement a conventional commits gate at my company that uses GitLab CI and eventually got to where I can do a fully integration. The problem I was having is following the posted instructions for installation led to mixed results even locally.
When I used pip install it did not put the main:cli entrypoint binary into the install path, it did put the commisery-verify-msg and another similar binary though but I had to manually integrate them into my path.
The only way I could get the main:cli i.e. the cm command to run was to do a pip install . on the cloned repo
I am not sure if this is a "Your mileage may vary" situation or not but I think if I could lend a suggestion, that you guys update your installation procedure to confirm the cm entrypoint is hit OR either update the documentation to include instructions to get the cm entrypoint to work or add the additional installation option of pip install . on the cloned repo.
I didn't want to make a cold PR but I think future users could benefit from the additional clarity or QoL update.
The text was updated successfully, but these errors were encountered:
gradytrain
changed the title
Suggestion for updating the installation instructions
documentation Suggestion for updating the installation instructions
Jan 31, 2025
gradytrain
changed the title
documentation Suggestion for updating the installation instructions
Suggestion for updating the installation instructions
Jan 31, 2025
Hi guys,
Hope you guys at TomTom are all doing well. I am starting to implement a conventional commits gate at my company that uses GitLab CI and eventually got to where I can do a fully integration. The problem I was having is following the posted instructions for installation led to mixed results even locally.
When I used pip install it did not put the main:cli entrypoint binary into the install path, it did put the
commisery-verify-msg
and another similar binary though but I had to manually integrate them into my path.The only way I could get the main:cli i.e. the
cm
command to run was to do apip install .
on the cloned repoI am not sure if this is a "Your mileage may vary" situation or not but I think if I could lend a suggestion, that you guys update your installation procedure to confirm the
cm
entrypoint is hit OR either update the documentation to include instructions to get thecm
entrypoint to work or add the additional installation option ofpip install .
on the cloned repo.I didn't want to make a cold PR but I think future users could benefit from the additional clarity or QoL update.
The text was updated successfully, but these errors were encountered: