Improve accessibility of CONTRIBUTING.md #147
Assignees
Labels
stale
Marked by labeler
Comments
bethaniley
added
the
IOI grant
|
This issue has been inactive for more than 90 days. If there is no further activity, it will be automatically closed in seven days time. You can reopen the issue if it is still relevant. |
|
Keep open |
LukasWallrich
removed
the
IOI grant
|
This issue has been inactive for more than 90 days. If there is no further activity, it will be automatically closed in seven days time. You can reopen the issue if it is still relevant. |
|
Keep open
*Lukas Wallrich*
1001 Valegro House // London SE10 9LJ
***@***.*** // +44 7591 975294 // +49 163 4704135
https://lukaswallrich.coffee
…On Sat, 18 Jan 2025 at 02:18, github-actions[bot] ***@***.***> wrote:
This issue has been inactive for more than 90 days. If there is no further
activity, it will be automatically closed in seven days time. You can
reopen the issue if it is still relevant.
—
Reply to this email directly, view it on GitHub
<#147 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOK6NGMANCLLCF3V3HJR5FD2LG2YTAVCNFSM6AAAAABLAO4NYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJZGQ3TKMRQG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I only recently discovered CONTRIBUTING.md - which could have prevented me from making some of the glossary mistakes. To avoid that, might it be worth adding a pull request template that requests contributors to ensure that they follow the guidance in that file?
Based on what I have seen when supporting others to contribute, the main challenge seems to be to get the PR process right. Here it might be good to provide more extensive guidance (maybe derived from usethis), but rewritten to focus on webpage rather than R package content? It might also be helpful to distinguish content contributions and technical contributions, where content contributors may not need to engage with the local testing at all if they don't want to learn about it?
A minor step towards accessibility would be to add the
usethisPR workflow that removes the need to deal with branches and figure out how to start a PR on github - instead, users only need to callpr_init()to create and switch to a new branch andpr_push()to push it and get to the right place to start the PR on GitHub.The text was updated successfully, but these errors were encountered: