Reference git commit for a release

[Cherry]

Continued from #55 as that was closed early.

If we're using a different release, is there no way to pass options to the set-commits command in sentry-cli? Even when not setting a release, I do not see releases tagged with specific git commits in Sentry.

The top 2 releases are once switching to this plugin - note there not being any git commits registered.

As per the docs, something like this would be great:

"refs": [{
    "repository":"owner-name/repo-name",
    "commit":"2da95dfb052f477380608d59d32b4ab9",
    "previousCommit":"1e6223108647a7bfc040ef0ca5c92f68ff0dd993" // optional
}],

[rvignesh89]

@kamilogorek this would be a useful feature for us as well. Any chance that you might take PR's for this?

[kamilogorek]

Sure, feel free to issue one

[rdsedmundo]

+1 for this one. Going to switch back for the sentry-cli, as not having this + ability to trigger a new deployment, makes the plugin a little bit useless.

[b0xtch]

PR #507 still needs to be merged to allow this feature.

[jsanchez034]

Looks like getsentry/sentry-cli#580 has added the ability to enable this feature

[dmitryrn]

@kamilogorek So what remains? As I can see from these PRs we need to add setCommits as option in this plugin?

[dmitryrn]

I probably can make a PR, just tried to use this.cli.releases.setCommits in src/index.js with success

[Cherry]

Looks like this was implemented in #139? AWESOME!

It's as simple as doing this, with other options like previousCommit available?

new SentryCliPlugin({
	release: 'abc,
	ignore: ['node_modules'],
	commit: process.env.GIT_HEAD
})

[kamilogorek]

You also need repo option to be defined, which is the name of repository you configured in the Sentry project options.

[dmitryrn]

I guess it should be closed now. Also see #142

[kamilogorek]

Done! Thanks everyone