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.

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

chore(github): issue template configuration and update issue templates #96

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

qdm12
Copy link
Collaborator

@qdm12 qdm12 commented Dec 19, 2024

Why this should be merged

How this works

  • .github/ISSUE_TEMPLATE/config.yml added to add a Github discussion contact link and disable blank issues
  • remove question issue template (see point above)
  • bug.md and feature.md geth issue templates removed (to simplify fork sync conflicts)
  • bug.yml and feature.yml libevm focused issue templates added (using the newer yml format)

value: |
Thanks for taking the time to fill out this bug report!

⚠️ Your issue will be instantly closed as not planned WITHOUT explanation if:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this an automated process?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

no 😄 just a warning in place so users don't forget to set the title of the issue and the libevm version. I had personally wayyyy too many issues without a title and/or without a version, which make things pretty horrible to maintain, and that reduced them, but we can remove this for now if you feel it's unecessary. I would recommend not automating in case it's still a serious issue, even without title/version 😮

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm ok with doing that but think we need to soften the language then. Please remove "instantly" and "WITHOUT explanation" as it's a little too aggressive.

Your issue will be closed as "not planned" if:

.github/ISSUE_TEMPLATE/feature.yml Outdated Show resolved Hide resolved
Copy link
Collaborator

@ARR4N ARR4N left a comment

Choose a reason for hiding this comment

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

Approved pending softening of the language, please.

value: |
Thanks for taking the time to fill out this bug report!

⚠️ Your issue will be instantly closed as not planned WITHOUT explanation if:
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm ok with doing that but think we need to soften the language then. Please remove "instantly" and "WITHOUT explanation" as it's a little too aggressive.

Your issue will be closed as "not planned" if:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants