When installing a package from git url this bug occurs on the first update.
The second update shouldn't be affected because the package gets convertet from git style to normal as part of the update.
This PR makes the code for the detail message more robust and adds sha's for git packages:
closes: #1056
To reproduce the bug reset a git package:
apm install thomaslindstrom/color-picker
cd ~/.atom/packages/color-picker
g stash
g reset --hard a296114f3d0deec519a41f4c62e7fc56075b7f01
g stash pop
replace the sha in package.json
Btw. what is the point of having git packages in the first place, when we convert them after the first update?
Description of the Change
When installing a package from git url this bug occurs on the first update. The second update shouldn't be affected because the package gets convertet from git style to normal as part of the update.
This PR makes the code for the detail message more robust and adds sha's for git packages:
closes: #1056
To reproduce the bug reset a git package:
apm install thomaslindstrom/color-picker
cd ~/.atom/packages/color-picker
g stash
g reset --hard a296114f3d0deec519a41f4c62e7fc56075b7f01
g stash pop
package.json
Btw. what is the point of having git packages in the first place, when we convert them after the first update?