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

added issue forms #2136

Merged
merged 2 commits into from
May 28, 2024
Merged

added issue forms #2136

merged 2 commits into from
May 28, 2024

Conversation

sdushantha
Copy link
Member

Added issues forms so that it is easier for users to write issues

Copy link
Member

@ppfeister ppfeister left a comment

Choose a reason for hiding this comment

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

For F+/F- reports, it may be beneficial to have an optional field for username(s) effected

If a site is susceptible to F+/F- with a specific pattern only (i.e. dots), that may speed up testing & patching

Copy link
Member

@ppfeister ppfeister left a comment

Choose a reason for hiding this comment

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

Minor correction to label

.github/ISSUE_TEMPLATE/site-request.yml Outdated Show resolved Hide resolved
Co-authored-by: Paul Pfeister <[email protected]>
@sdushantha
Copy link
Member Author

For F+/F- reports, it may be beneficial to have an optional field for username(s) effected

If a site is susceptible to F+/F- with a specific pattern only (i.e. dots), that may speed up testing & patching

I was thinking that such information could be added to the Additional Information textbox

@ppfeister
Copy link
Member

For F+/F- reports, it may be beneficial to have an optional field for username(s) effected
If a site is susceptible to F+/F- with a specific pattern only (i.e. dots), that may speed up testing & patching

I was thinking that such information could be added to the Additional Information textbox

Having dealt with the general public while trying to diagnose infra issues and such, I'm of the belief that very explicit directions are sometimes needed, else you get reports like #2126 "some of these don't work, but I'm not going to tell you which, btw this product sucks".

Although those types of reports are fairly rare here, so it's not a hard requirement. I think most contributors have been pretty good about their bug reports and it can probably be left out for now.

Copy link
Member

@ppfeister ppfeister left a comment

Choose a reason for hiding this comment

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

GTG

@sdushantha sdushantha merged commit 1cd8138 into master May 28, 2024
3 checks passed
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.

None yet

2 participants