diff options
| author | dundargoc <gocdundar@gmail.com> | 2024-05-01 15:39:46 +0200 |
|---|---|---|
| committer | dundargoc <33953936+dundargoc@users.noreply.github.com> | 2024-05-01 22:30:17 +0200 |
| commit | 631d5189adaaf54eb48e0b136df3466880edb19c (patch) | |
| tree | de6950b6d058d7741946b96ab7034c2d14d0abd2 /test/functional/lua/ui_event_spec.lua | |
| parent | 947335be915fc83e16f83befa22a6ad8eb84ab6f (diff) | |
| download | rneovim-631d5189adaaf54eb48e0b136df3466880edb19c.tar.gz rneovim-631d5189adaaf54eb48e0b136df3466880edb19c.tar.bz2 rneovim-631d5189adaaf54eb48e0b136df3466880edb19c.zip | |
ci: improve default backport pull request title
`[Backport release-x.y]` will no longer be part of the pull request
title. This means the PR titles will go from looking like
```
[Backport release-0.9] fix(languagetree): remove double recursion in LanguageTree:parse
```
to
```
fix(languagetree): remove double recursion in LanguageTree:parse
```
The benefit of this is that pull requests merged with the "Squash and
Merge" strategy (which uses the PR title as the commit message), will
still follow the conventional commits specification. This will help
tools that rely on conventional commits such as git-cliff.
The `backport` label is added to backported PRs to help distinguish
between backport PRs with regular PRs in the "Pull Requests" tab on
github.
To reduce confusion with the `backport` label, the label to trigger the
backporting has been changed from `backport release-x.y` to
`ci:backport release-x.y`. This is also more consistent with other
labels that trigger a CI job which all use the `ci:` prefix.
Diffstat (limited to 'test/functional/lua/ui_event_spec.lua')
0 files changed, 0 insertions, 0 deletions