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

Explain auto-close policy in ISSUE_TEMPLATE.md #1084

Merged
merged 2 commits into from
Feb 13, 2023
Merged

Conversation

NateEag
Copy link
Contributor

@NateEag NateEag commented Feb 12, 2023

@github-actions
Copy link

Hello. Thanks for opening a PR on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed.

That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there.


Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

@github-actions github-actions bot closed this Feb 12, 2023
@SleeplessByte SleeplessByte reopened this Feb 12, 2023
Copy link
Member

@kotp kotp left a comment

Choose a reason for hiding this comment

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

Not a disapproval, but something to consider.

We might also follow the Exercism recommendation for Markdown1, here, to be consistent.

Notable:

  • Single sentence per line
  • Reference links

Comment on lines 2 to 8
Hello. Thanks for opening an issue on Exercism - we really appreciate your interest in helping!

We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post: https://exercism.org/blog/freeing-our-maintainers. **As such, all issues and PRs in this repository are being automatically closed.**

That doesn’t mean we’re not interested in your ideas, or that if you’re stuck on something we don’t want to help. The best place to discuss things is with our community on the Exercism Community Forum: https://forum.exercism.org. If necessary, we will open actionable issues here about what needs to change.

If you do open an issue, the auto-close comment will include a link to create a discussion on the forum.
Copy link
Member

Choose a reason for hiding this comment

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

These lines do not match the (technical) style of the lines replaced.

.github/ISSUE_TEMPLATE.md Outdated Show resolved Hide resolved
@iHiD
Copy link
Member

iHiD commented Feb 13, 2023

@NateEag Thanks for opening this :) I've left a suggestion.

@iHiD
Copy link
Member

iHiD commented Feb 13, 2023

We might also follow the Exercism recommendation for Markdown, here, to be consistent.

@kotp I actually think we don't want to do this here as this text is never rendered so the rules don't apply. Instead the text is shown as is, with normal paragraph formatting, is much more readable I think.

@NateEag
Copy link
Contributor Author

NateEag commented Feb 13, 2023

@kotp Thanks for the suggestion! I went with plain paragraph formatting for the reasons @iHiD outlined.

@iHiD iHiD merged commit edee207 into exercism:main Feb 13, 2023
@iHiD
Copy link
Member

iHiD commented Feb 13, 2023

Thanks :)

@kotp
Copy link
Member

kotp commented Feb 13, 2023

No problems. It is not that important, this file does not churn like others can. But the reasons are not only for rendering, but for "a sentence change should not need to show diff for the entire paragraph" so the reasoning is not only for rendering purposes, they are for maintenance and diff noise as well.

@NateEag NateEag deleted the patch-3 branch February 14, 2023 14:37
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.

4 participants