Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
Is there a preferred process for making minor fixes such as typos on codidact.org? I've made a commit to a fork but I didn't want to raise a GitHub issue and make a pull request without checking t...
Question
support
#1: Initial revision
by
trichoplax
·
2022-09-16T12:32:02Z (about 2 years ago)
Process for fixing a typo on codidact.org
Is there a preferred process for making minor fixes such as typos on codidact.org? I've made a [commit to a fork] but I didn't want to raise a GitHub issue and make a pull request without checking the process first, as it's such a tiny change. - Should it be included in another issue which addresses the same file? - Should it be added to a dedicated issue for typos and wait until several typos can be fixed at once? - Should it have its own issue even though it's small? - Should it be ignored - is it too small to change? I decided to take up time with a community discussion here on Meta rather than risk wasting developer time by making an assumption about the process on GitHub. I couldn't find anything about this is in the [contributing guidelines] - would it be helpful to add something about typos there? [commit to a fork]: https://github.com/trichoplax/landing-page/commit/e2747229e5cc969feb7fcd8f1c4e31e178af130d [contributing guidelines]: https://github.com/codidact/.github/blob/6cfc2117cacda4640236540f5dc6ccbbaa13dcf0/CONTRIBUTING.md