Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Notifications
Mark all as read
Q&A

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.

Process for fixing a typo on codidact.org

+1
−0

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?

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+2
−0

You can either raise an issue on GitHub or post a bug report here on Meta. Even the smallest of bug reports are appreciated, and that includes typos. You can also make a pull request directly to fix the problem - don't worry that it's a small change.

I don't know when it will be deployed, because historically, there's been a roadblock with deploying the .org page, but if we know that there's something waiting to be deployed, I can poke the relevant people until it gets done.

I'm actually hoping that some work will be done on that page relatively soon (I have some things in mind that I'd like to improve or add). If that does happen, hopefully we'll address that deployment roadblock at the same time.

Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Which branch to target in a pull request (3 comments)

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!

Like what we're doing? Support us! Donate