Jongwook Choi bcd111bd12 ci: write the correct cherry-picked commit id when backporting ...

Problem: Commits backport-merged to release branches are cherry-picked
from the original commits in the PR from a fork repository, NOT the
actual commit that are merged to neovim/neovim (HEAD). Therefore the
commit reference in the commit message `cherry picked from commit ...`
usually refers to a commit that does NOT exist in the repository,
given that our preferred way of merging PR (rebasing, squashing, etc.)
would rewrite commits.

Solution: Turn on new feature 'detect_merge_method' of backport-action
workflow.

2024-01-01 15:17:56 +01:00

..

actions

ci: create setup action

2023-12-01 16:59:23 +01:00

ISSUE_TEMPLATE

docs: move minimum reproduction template from wiki to repo

2023-12-12 18:32:45 +01:00

scripts

ci: disable libintl on mac release

2023-12-26 22:46:10 +01:00

workflows

ci: write the correct cherry-picked commit id when backporting

2024-01-01 15:17:56 +01:00

dependabot.yml

ci: use "ci" as the commit type for dependabot updates

2023-03-24 05:39:18 +01:00

FUNDING.yml

funding: Bountysource Salt -> GitHub Sponsors & Open Collective [ci skip] (#12959)

2020-09-21 20:47:02 +02:00

SECURITY.md

docs: add security policy (#17338)

2022-12-22 13:20:19 +01:00