Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update GitHub issue templates #1549

Merged
merged 1 commit into from
Nov 10, 2023
Merged

Update GitHub issue templates #1549

merged 1 commit into from
Nov 10, 2023

Conversation

tnozicka
Copy link
Member

@tnozicka tnozicka commented Nov 9, 2023

Description of your changes:
This PR moves the existing GitHub issue templates to structured YAML and restructures them, now that we have must-gather.

Which issue is resolved by this Pull Request:
Resolves #1366

@tnozicka tnozicka added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/machinery Categorizes issue or PR as related to Makefile, scripts or similar changes. labels Nov 9, 2023
@scylla-operator-bot scylla-operator-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tnozicka

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@scylla-operator-bot scylla-operator-bot bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 9, 2023
rzetelskik
rzetelskik reviewed Nov 9, 2023
View reviewed changes
Copy link
Member

@rzetelskik rzetelskik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a way to see what it looks like after parsing?

.github/ISSUE_TEMPLATE/bug-report.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug-report.yaml Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug-report.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug-report.yaml Show resolved Hide resolved
.github/ISSUE_TEMPLATE/ci-flake.yaml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/feature-request.yaml Outdated Show resolved Hide resolved
@tnozicka
Copy link
Member Author

is there a way to see what it looks like after parsing?

i think you can test it in settings but not now because we are transitioning from the md files

@rzetelskik
Copy link
Member

/lgtm
thanks

@scylla-operator-bot scylla-operator-bot bot added the lgtm Indicates that a PR is ready to be merged. label Nov 10, 2023
@scylla-operator-bot scylla-operator-bot bot merged commit 002e228 into scylladb:master Nov 10, 2023
8 checks passed
@rzetelskik rzetelskik mentioned this pull request Nov 10, 2023
Merged
@tnozicka tnozicka deleted the gh-templates branch November 10, 2023 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@zimnx zimnx Awaiting requested review from zimnx

@rzetelskik rzetelskik Awaiting requested review from rzetelskik

Assignees

@rzetelskik rzetelskik

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/machinery Categorizes issue or PR as related to Makefile, scripts or similar changes. lgtm Indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Require must-gather in bug reports
2 participants
@tnozicka @rzetelskik