1.9 KiB
How to submit a fix to an IOCCC entry
If you see a problem with an IOCCC entry, first check the known bugs file. In some cases what you might think of as a bug is instead a known feature. In some cases the bug is known, but no fix has ever been submitted. In other cases you may have found a new problem.
If you do have a fix, and the known bugs file does not recommend against fixing it, then please consider opening a GitHub pull request against the master branch of the ioccc-src/winner repo repo.
BTW: A problem is not limited to the code itself. Fixing typos in files such as "README.md" files, fixing issues in a "Makefile", or otherwise correcting an IOCCC winner is VERY MUCH WELCOME! Please use the same GitHub pull request process against the master branch of the ioccc-src/winner repo repo.
NOTE: some of the issues in the bugs.md file includes just missing files and we welcome these too!
Please also help us fix typos and / or otherwise improve the write-up of how IOCCC winning entries are presented!
In any event we will happily add you to the thanks-for-fixes.md file for your help!
And of course, an IOCCC winner may update their own entries (metadata as well as source code and any extra files) by opening a GitHub pull request against the master branch of the ioccc-src/winner repo repo.
Note that we're much more inclined to accept an author's fixes but the judges have the final say in the matter.