Carlos A Becker 797a1ccc5f

feat: release with target_commitish in another repo ...

We should not imply the target_commitish, as some users might want to
have the code in one repo and the releases in another (e.g. private
code, public releases), so the commit might not be there.

We should instead allow the user to set the `target_commitish` (or not),
and pass it down to the github api.

refs 95bba02211a2b88426826ff36a3fd1b424a1d5a7
refs #3044
refs #3330

Signed-off-by: Carlos A Becker <caarlos0@users.noreply.github.com>

2022-08-22 21:31:28 -03:00

..

testdata

refactor: better code organization (#757)

2018-08-14 23:50:20 -03:00

config_archive_files_test.go

feat(yaml): upgraded from yaml.v2 to yaml.v3 (#3004)

2022-03-29 14:00:53 -03:00

config_array_test.go

feat(yaml): upgraded from yaml.v2 to yaml.v3 (#3004)

2022-03-29 14:00:53 -03:00

config_build_hook_test.go

feat(yaml): upgraded from yaml.v2 to yaml.v3 (#3004)

2022-03-29 14:00:53 -03:00

config_homebrew_dependency_test.go

chore: gofumpt & lint (#2190)

2021-04-25 14:20:49 -03:00

config_slack_test.go

feat(announce): added Slack notification options (#2988)

2022-03-30 09:42:59 -03:00

config_test.go

refactor: use os and io instead of ioutil (#2676)

2021-11-21 11:10:08 -03:00

config.go

feat: release with target_commitish in another repo

2022-08-22 21:31:28 -03:00