build: use git default short commit-id

[JayFate]

before this commit

const commit = execa.sync('git', ['rev-parse', 'HEAD']).stdout.slice(0, 7)
console.log(`commit`, commit) 
// commit a0e7dc3

after this commit

const commit = execa.sync('git', ['rev-parse', '--short', 'HEAD']).stdout
console.log(`commit`, commit) 
// commit be78cf43

[JayFate]

@sxzz Do you have a minute to review this PR ? THX

[yyx990803]

What is the point of this? The original uses 7 chars which is consistent with the GitHub short format.

[sxzz]

@yyx990803

It may create a non-unique commit id by slicing 7 lengths. (Although the current probability is very unlikely)

you can ask git rev-parse --short for the shortest and yet unique SHA1

Further read: https://stackoverflow.com/questions/18134627/how-much-of-a-git-sha-is-generally-considered-necessary-to-uniquely-identify-a

[Justineo]

After looking at where we are using these short commit ids, I think we should keep this consistent with GitHub’s format.

[JayFate]

@yyx990803 @sxzz @Justineo Updated.

Is this commit necessary any more ?

[github-actions]

Size Report

Bundles

File	Size	Gzip	Brotli
runtime-dom.global.prod.js	85.9 kB	32.7 kB	29.5 kB
vue.global.prod.js	132 kB	49.3 kB	44.3 kB

Usages

Name	Size	Gzip	Brotli
createApp	47.9 kB	18.8 kB	17.2 kB
createSSRApp	50.6 kB	20 kB	18.2 kB
defineCustomElement	50.3 kB	19.6 kB	17.9 kB
overall	61.2 kB	23.7 kB	21.6 kB