| tag | 3adb1ecacb6300fa91c4e7357f08305efdefef63 | |
|---|---|---|
| tagger | Volkan Yazıcı <volkan@yazi.ci> | Thu Oct 19 16:04:56 2023 +0200 |
| object | 13ee5ca880ef515b69fb1fc6b5fe2e1807e48be6 |
10.2.0
| commit | 13ee5ca880ef515b69fb1fc6b5fe2e1807e48be6 | [log] [tgz] |
|---|---|---|
| author | Piotr P. Karwasz <piotr.github@karwasz.org> | Wed Oct 18 20:42:11 2023 +0200 |
| committer | Piotr P. Karwasz <piotr.github@karwasz.org> | Wed Oct 18 20:42:11 2023 +0200 |
| tree | 02b5221eb4387b5eded856c034c96f12702a7ac1 | |
| parent | d9809253c3be1a548ca1e54a5e9a1b5d05748be6 [diff] |
Add --force to the release pushes performed by the CI If the `deploy` step fails, the Github Actions run will be two commits behind the tip of the branch. We must allow the workflow to remove the last two (automatic) commits from the branch. Repos should use a `concurrency` setting to prevent Github Actions from removing manually added commits.