-
Notifications
You must be signed in to change notification settings - Fork 59
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
ignore-children
comment incentive config
#772
Comments
GitHub has this really annoying "feature" that makes generated issues from comments indented heavily with ten spaces in front By parsing the |
/start |
Tips:
|
Do you have any updates @GaryThisSidee? If you would like to release the bounty back to the DevPool, please comment |
Can I take this issue after like 3 days |
Looking forward to this feature getting merged in. This and ChatGPT interpreting if the comments are on topic are all that we need to turn up the comment incentives high. |
Do you have any updates @GaryThisSidee? If you would like to release the bounty back to the DevPool, please comment |
Do you have any updates @GaryThisSidee? If you would like to release the bounty back to the DevPool, please comment |
1 similar comment
Do you have any updates @GaryThisSidee? If you would like to release the bounty back to the DevPool, please comment |
well waiting for it to be approved |
Do you have any updates @GaryThisSidee? If you would like to release the bounty back to the DevPool, please comment |
@GaryThisSidee - Releasing the bounty back to dev pool because the allocated duration already ended! |
Yikes. We should set a special property on every element that indicates whether the parser should recurse or stop.
Originally posted by @pavlovcik in #648 (comment)
Ten Space Blockquote
GitHub has this really annoying "feature" that makes generated issues from comments indented heavily with ten spaces in front
" "
which makes the line render as a code block. Can we detect this and not credit it? It's effectively supposed to be a blockquote (ignored) but its being credited as a code block.By parsing the
raw
comment this should be easy to detect the ten spaces in front of a line.The text was updated successfully, but these errors were encountered: