view .github/ISSUE_TEMPLATE/feature_request.md @ 35183:9a1ac66c788d

CI: Upload failed screendump tests when run in github actions Commit: https://github.com/vim/vim/commit/8314de8fd4aa4d18fc524f960f5d683a2d8cba32 Author: Christian Brabandt <cb@256bit.org> Date: Wed May 15 21:48:11 2024 +0200 CI: Upload failed screendump tests when run in github actions It's a bit of a pain to debug failing screendump tests without knowing exactly what went wrong. Therefore include actions/upload-artifact for the Github CI runners and have them uploaded those failing screen dump tests automatically. Let's add this step to each of the Linux/MacOS/Windows workflows but do not duplicate the code, factor it out to a single file .github/actions/screendump/action.yml and reference this one from the main ci.yml file Example: https://github.com/chrisbra/vim/actions/runs/9085493619 closes: #14771 Co-authored-by: dundargoc <gocdundar@gmail.com> Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Wed, 15 May 2024 22:00:04 +0200
parents 4fdc8319ab24
children
line wrap: on
line source

---
name: Feature request
about: Suggest an enhancement for Vim
title: ''
labels: enhancement

---

_Instructions: Replace the template text and remove irrelevant text (including this line)_

**Is your feature request about something that is currently impossible or hard to do? Please describe the problem.**
A clear and concise description of what is hard to do. Ex. It is difficult to [...] when [...]
(If it is related to runtime files, please check their header for where to discuss enhancements.)

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.