#329: Update issue templates to spring 2025 standard#330
Conversation
* added issue type to templates * removed tasklist from Epic and Spike
benedeki
requested review from
ABLL526,
Zejnilovic,
dk1844,
lsulak and
salamonpavel
as code owners
There was a problem hiding this comment.
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
.github/ISSUE_TEMPLATE/spike_task.md:5
- [nitpick] The type value 'Task' in the Spike template might be too generic given the template name is 'Spike'. Consider using a type value like 'Spike' for clearer intent.
type: 'Task'
.github/ISSUE_TEMPLATE/question.md:5
- [nitpick] The type value 'Task' in the Question template could be misleading; aligning it with the template name (e.g., 'Question') may improve clarity.
type: 'Task'
|
Report: Jacoco Report on
No changed file in reports. |
|
Report: Jacoco Report on
No changed file in reports. |
|
Report: Jacoco Report on
No changed file in reports. |
|
Report: Jacoco Report on
No changed file in reports. |
benedeki
added
no RN
| # | ||
|
|
||
| name: Check PR Release Notes in Description | ||
| name: Check PR Release Notes Presence Check |
There was a problem hiding this comment.
| name: Check PR Release Notes Presence Check | |
| name: Check PR Release Notes Presence in Description |
There was a problem hiding this comment.
I am little torn on this. Adding the info into the name is good. But my experience is, that if it differs from filename or workflow name, it leads to confusion.
There was a problem hiding this comment.
ok, so let's change the job name, too. ok?
There was a problem hiding this comment.
It is the same now, isn't it?
There was a problem hiding this comment.
It is not. To be same there is need to rename the job name to "Release Notes Presence Check"
benedeki
deleted the
feature/329-update-issue-templates-to-spring-2025-standard
branch
Closes #329